Who writes the guides and articles on Convertlo?

The Convertlo editorial team — a small group who built the site and use these tools daily. Articles are collaborative, so they're attributed to the team rather than individual names.

How do you verify technical claims like file size comparisons?

We run conversions on real test files and measure actual outputs. Compression ratio claims come from our own testing across representative image sets, not from copied industry statistics.

How quickly are errors corrected after being reported?

Our target is within 24 hours of confirming the error. The dateModified in the article schema is updated and substantive changes are noted at the bottom of the article.

How often is content reviewed and updated?

We update articles when a browser ships a relevant update, a new format version is released, or a reader reports an error — not on a fixed schedule.

Does Convertlo have a relationship with format developers or software vendors?

No. We have no commercial arrangement with any format developer or tool vendor. All format comparisons are based on our own testing.

Editorial Policy — How We Research and Write Content

Q: Does Convertlo use AI to write its content?

AI tools may assist with early drafts, but every article is reviewed, rewritten where needed, and verified by a human editor. Technical claims are always checked against primary sources.

Our Editorial Principles

Every article, guide, and comparison page on Convertlo is written to be technically accurate, jargon-free for a general audience, and genuinely useful — not to fill keyword quotas or generate pages for search engines.

🎯

Accuracy First

Technical claims are verified against official format specifications, browser documentation, and first-hand testing.

🔍

Transparent Sources

Where we cite statistics (file size savings, browser support percentages), we state the basis for those numbers.

🔄

Regular Updates

We update articles when browser support changes, new format versions are released, or tool behavior changes.

✏️

Fast Corrections

Factual errors reported by readers are corrected promptly, typically within 24 hours of confirmation.

How We Research an Article

1

Primary source review

We consult official documentation first — format specifications (ISO, W3C, IETF RFCs), codec developer documentation (FFmpeg, libvpx, libaom), and browser compatibility data from MDN and Can I Use.

2

Hands-on testing

We test conversions using the actual tools we recommend. File size comparisons use representative test images. Browser support claims are verified in current stable releases of Chrome, Firefox, Safari, and Edge.

3

Technical review

Technical accuracy is reviewed before publication. Any claims about compression ratios, quality differences, or compatibility are double-checked against source data.

4

Plain language editing

We rewrite technical content for clarity. Our audience includes non-technical users who just need their file converted — not RFC authors. We avoid unexplained jargon.

5

Publication and dating

Every article shows a publication date and "last modified" date in the article schema. We do not backdate articles or hide update history.

What We Cover — and What We Don't

Convertlo covers browser-based file conversion: the technical properties of formats, when to use which format, how conversion quality works, and how to use our tools. We do not cover topics outside our area of genuine expertise.

We do not:

Fabricate benchmark data — all compression ratios and file size comparisons come from real tests on real files
Publish AI-generated content without review — any AI assistance in drafting is reviewed and corrected by a human editor before publication
Write sponsored "reviews" disguised as editorial content — we have no financial relationship with format developers, codec vendors, or software companies whose products we discuss
Recommend paid tools without disclosure — if we mention a paid product, we say so

Update and Correction Policy

File formats and browser APIs evolve. An article that was accurate in 2024 may need updating by 2026. We monitor:

Browser support changes (Can I Use, MDN, browser release notes)
New format versions and specification updates
Changes to our own tools that affect conversion behaviour
Reader-reported corrections submitted via our social channels

When we make a meaningful correction to an article, we update the dateModified in the article schema and note the change at the bottom of the article where relevant.

To report an error, contact us via Facebook or X (Twitter). We aim to respond within 24 hours.

Author Information

Articles on Convertlo are written by the Convertlo Editorial Team — a small group of people who work on this site and use these tools regularly. You can read more about our team on the About page.

We attribute articles to the Convertlo Editorial Team rather than individual pen names because our team is small and collaborative — multiple people typically contribute to each article through research, writing, and review.

Independence and Monetisation

We do not accept payment to write about specific products, formats, or services. All conversion tools listed on this site are free to use with no commercial arrangement with the developers.

Questions About Our Content

The Convertlo editorial team — a small group of people who built this site, use these tools daily, and have worked with file formats professionally. We attribute articles to the "Convertlo Editorial Team" rather than individual names because articles are genuinely collaborative: one person might write the initial draft, another verifies the technical claims, and a third edits for clarity. Pen names would misrepresent that.

We sometimes use AI tools to help with early drafts, but every article published on Convertlo is reviewed, rewritten where needed, and verified by a human editor before going live. We do not publish raw AI output. Technical claims — compression ratios, browser support figures, format specifications — are always checked against primary sources regardless of how the initial draft was produced.

We run the conversions ourselves on real test files and measure actual outputs. For a claim like "WebP is 25–34% smaller than PNG at equivalent quality," we convert a set of representative images — photographs, graphics, screenshots — using Convertlo's own tool and measure the size difference across each type. We don't copy industry statistics without checking them ourselves. If a figure comes from an external source like Google's WebP documentation, we say so.

Our target is within 24 hours of confirming the error. For clear factual mistakes — wrong browser support date, incorrect file size claim — we fix immediately once we've verified the correct information. For more nuanced corrections where the "right answer" is debated (like quality comparisons between codecs), we may update with additional context rather than a simple correction. We update the dateModified in the article schema and note substantive changes at the bottom of the article.

We review articles when: a browser ships a relevant update (like a new format gaining Safari support), a new format version is released, we spot something that's become outdated, or a reader reports an error. We don't update content on a fixed schedule — we update it when there's a genuine reason to. Articles with a "last modified" date well into the past should be read with that in mind; browser support tables in particular age quickly.

No. We have no commercial arrangement with Google (WebP, AVIF), the Alliance for Open Media (AVIF, AV1), FFmpeg, or any other format developer or tool vendor whose work we discuss. When we say WebP has better compression than JPEG, it's because our tests show that — not because anyone paid us to say it. We also don't run affiliate links for paid software we mention in comparisons.

How We Research and Write Our Content