How we write and test
Every page on deskumo is meant to help you get a job done and understand what happened. These are the rules we follow.
We test before we write
Each tool is tested with real files before its page is published. Numbers you see under “What we measured” come from a script that runs the same code as the tool in Chrome on a 4-core test computer. Test photos are public sample images from the scikit-image project; test PDFs are generated documents with text and photos on every page. Speeds on your phone or computer will differ, which is why we always say what we tested on.
Where a number is calculated rather than measured, such as password strength, QR code sizes or calendar dates, we compute it with the same logic the tool uses and check it a second way.
We say what a tool can’t do
Every tool page has a section on limits. If a browser can’t do something reliably, such as reading HEIC photos outside Safari or opening password-protected PDFs, we say so instead of hiding it.
Sources
We rely on primary sources: the WCAG standard for contrast, the Unicode standard for characters, the IANA time zone database built into your browser for time zones, and exact legal definitions for units. Guides link to the tool that does the job and explain the reasoning so you can check it.
Eight languages
Pages are written directly in each language from the same verified facts, rather than translated sentence by sentence, so that examples, number formats and search terms feel natural. We don’t yet have a native-speaking editor for every language. If something reads awkwardly or is wrong, please tell us.
Ads and independence
No company pays to be mentioned or recommended on deskumo. Advertising is served by Google AdSense and is kept separate from the content and away from the tool controls.
Corrections
Found a mistake? Write to justin.cho@plexsor.ai with the page address. We fix confirmed errors and update the “last updated” date on the page.