How AI was used here

Parts of this site were built with the help of AI: the code that converts your files, a good deal of the text that explains it, and the translation of that text into seven languages.

This page says which parts, what we check and what we cannot, and what to do if you find something that is simply wrong.

Which parts

The code. The conversion engines, the pages around them and the tests that check both were written with AI assistance and reviewed before they shipped.

The text. The format descriptions, the comparison pages, the unit notes and the explanatory sections were drafted the same way — and then translated into German, Spanish, French, Portuguese, Italian, Dutch and Hindi.

What that does not mean is that anything here was published unread. Every page was gone over before it went up, and what a page claims about a conversion is checked against what the code actually does.

Where the risk actually sits

AI gets things wrong in a particular way: it is fluent. A mistaken sentence about a file format reads exactly like a correct one. That is worse than an obvious error, because there is nothing for a reader to notice and nothing for a reviewer to catch their eye on.

Two places deserve the most suspicion. The factual claims about formats — what a format can store, what a conversion loses, which of two things is bigger — because they are specific, confident and checkable only by someone who already knows. And the seven translations, where a subtle mistake cannot be spotted by anyone who does not read that language, and where a sentence can be grammatical, natural and still say something the English never said.

What is checked by machine, and what is not

The numbers are not written. Page counts, format counts, conversion counts and the factors in every unit calculator come from one registry and are inserted into the text. Prose here cannot quote last month’s figure, because prose here does not hold figures.

What a conversion does is bound to a test. Where a page says the text in a PDF stays selectable, or that no pixel changes, a test opens the result and checks. A claim that stops being true fails the build rather than sitting on the page.

The privacy claims are the ones you can check yourself, and that is the point of them. Open your browser’s network tab and convert something: you will see the page, and the statistics and advertising requests, and nothing carrying your file. You do not have to take our word for that — or an AI’s.

What no test can check is the prose itself. A well-written sentence that is factually wrong passes every check we have. That is the gap this page exists to name, and the reason the next section matters more than the rest of it.

The legal pages

The privacy notice, the terms and the imprint were drafted with AI help as well. They were written to describe what this site really does rather than to be generic boilerplate — the privacy page is changed in the same commit as the behaviour it describes, which is why it can say what a request carries and what it does not.

They are not legal advice and they are not a substitute for it. If you work in this field and something in them is wrong, incomplete or out of date, that is a message we would particularly like to get.

Found something wrong? Please tell us

Write to info@quinvert.com. Naming the page and saying what is wrong is enough — you do not have to explain why, and you do not have to be sure.

Corrections are made and the date at the bottom of the page changes with them. A page is not quietly edited to look as though it was always right.

This is the single most useful thing anyone can send us, and it is why this page exists at all instead of a badge saying the site was reviewed by a human.