About this site
How we test, write and correct what you read on PNGToolbox
Every number on this site comes from a script we publish, and every technical claim is checked against a primary source. Here is the process, the funding, and how to correct us.
At a glance
- Guides are written for one audience: people with a file in their hand and a decision to make.
- Quantitative claims come from tests we run ourselves and publish, including the raw CSV and the scripts.
- Technical claims about formats, browser behaviour and platform rules are checked against primary sources — specifications, vendor documentation and platform help centres.
- We publish a "last reviewed" date on every guide and correct mistakes in place, noting what changed.
- The site is funded by advertising. Advertisers have no input into what we write.
Who writes this site
PNGToolbox is a small independent site run by a developer who needed a WebP converter that did not upload customer files to somebody else's server, and who got tired of format guides that repeat folklore without measurements. The guides exist because the same questions arrive by email week after week: why did my PNG get so much bigger, why does my transparent logo have a white edge, why does this one file open in Photoshop and not in the shop's upload form.
Drafting is assisted by software, and we say so rather than pretend otherwise. What makes the output trustworthy is not the drafting tool but the checks after it: every figure published on this site is produced by a script we ship, and every claim about how a format or a platform behaves is traced to a primary source before publication.
How the numbers are produced
Most of what we publish about file size is a measurement, not an estimate, and we treat it the way a lab notebook is treated.
- The test corpus is generated, not borrowed.
bench_kit.pybuilds the images we test with: a photographic texture, a UI screenshot, a transparent logo, flat vector-style artwork, a cutout product photo and a smooth gradient. Generated images avoid licensing questions and, more usefully, let anyone else rebuild byte-identical inputs. - The measurement script is published with every study.
bench_kit.pyre-runs the conversion, records sizes, PSNR, SSIM and alpha statistics, and writes the CSV files we link to from each guide. - Encoder versions are stated. A number without an encoder build is not reproducible. Our current results were produced with Pillow 11.0.0 on 22 October 2026.
- We report what the measurement says, including the awkward parts. When PSNR failed to improve between JPEG quality 40 and quality 95 on a screenshot, that went into the article rather than being smoothed over, because it is the most useful finding in the table.
- Claims about your device are verified in a browser. Converter behaviour that depends on the browser decoder — animated WebP handling, WebP re-encoding support, canvas colour handling — is checked in real browsers before it is described.
Where claims come from
Format behaviour is documented in specifications and vendor docs, and we treat those as the source of truth: the PNG specification for chunk structure and colour types, Google's WebP documentation for compression modes, MDN and caniuse for browser support. Platform rules — upload limits, required dimensions, alpha handling — are read from the platform's own help centre, with the URL listed in the guide.
When a primary source does not exist for something people repeat, we say so instead of dressing up an estimate as a fact. "Nobody publishes an official number for this" is a perfectly good sentence.
Dates, revisions and corrections
Every guide carries a publication date and a review date. A review means we reopened the page, re-ran anything that could have changed, and updated the wording if the software or the platform moved. Guides that have not been reviewed recently are marked as such rather than silently re-dated.
When we get something wrong, we fix it in place and describe the change at the bottom of the page. Silent edits to technical claims are the fastest way to lose a reader's trust, and it costs us nothing to be explicit.
Disagreements are welcome and are the main way this site improves. The contact page reaches a human, and a report that includes the file, the browser and the steps is usually resolved in a day.
What we do not do
- We do not upload your images anywhere. Conversion runs in your browser, which is why the tools work offline once loaded and why you can verify the claim in your browser's network panel.
- We do not publish a tool we have not checked against real files. Each release is verified against the output checklist on the output testing page: batch conversion, resizing, transparency preservation, colour sampling, ZIP packaging and mobile layouts.
- We do not accept payment for positive coverage, and we do not write about a format because someone asked us to.
- We do not ask you to create an account to find out what a file size will be.
How the site is funded
Advertising pays the hosting bill. Ads are served by Google AdSense and are labelled as advertising. Advertisers do not see our drafts, cannot request a mention and have no influence on the content of a guide. If an article ever contains a sponsored element, it will say so at the top of the page.
Tracking is limited to what the ad and analytics scripts require; the privacy policy lists exactly what is collected and what is not. Images you open in a tool are never part of that data — they are read by your browser and never leave your device.
Contact and authorship
The site is edited under the name PNGToolbox Editorial. Questions about a specific measurement, a request to re-run a test with different settings, or a correction all go to the same address on the contact page. If you want to reproduce a benchmark on your own hardware, the scripts are published beside the results and we will happily compare numbers.
Convert WebP files to PNG or JPG — in your browser
Batch conversion, ZIP download, transparency kept. No upload.
Sources
- Google Search Central: creating helpful, reliable, people-first content — https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Google Search Central: quality rater guidelines (E-E-A-T definitions, PDF) — https://guidelines.raterhub.com/searchqualityevaluatorguidelines.pdf
- PNG (Portable Network Graphics) specification — https://www.w3.org/TR/png-3/
- WebP compression documentation — https://developers.google.com/speed/webp/docs/compression