PDF Compare in the browser is not a generate

/free-tools/pdf-compare never spends a credit. Do not pay a model to do an in-browser file job.

PDF Compare renders two PDFs and pixel-diffs them page by page, highlighting changed regions. It runs in your browser. Nothing is uploaded. Nothing is sent to a model. There is no account gate and no generation meter. That is the product constraint for the whole free-tools shelf: Canvas, the File API, or arithmetic on the visitor's machine. A "compare" that quietly called Veo, an OCR model, or a chat completion would be a generate wearing a utility label.

Versely has no free tier for generation. Every model call costs credits. Browser utilities sidestep that because they cost nothing to run. Use this tool when the job is "did this proof change." Do not prompt a video or image model to "show me the difference between these PDFs."

The engine is your machine

The file you choose is read into memory locally, compared there, and offered back as a view. Network off, it still works. That is also why it is actually free: no hardware of ours is in the loop. What it costs is the other book — credit formulas for per-second video, per-character voice, per-megapixel stills, caption burns, editor exports. PDF Compare is not in that book. If a job is in that book, it is not this tool.

Do not paste pages into an AI video generator and ask for a "diff video." You will spend a clip rate to invent a visualisation of a proof. You will not get a pixel-accurate overlay. You will get a generate. The compare already highlights changed blocks on a diff view. That is the artefact.

Pixel diff is not a text diff

This is a visual compare. Two files with identical words and different fonts, kerning, or anti-aliasing will light up. That is usually what you want when checking a proof: the page as printed, not the Unicode. A word swapped for a synonym in the same position, same font, same size, can be invisible at a coarse tolerance. For a textual diff, extract both files to text first. Do not ask a model to "read both PDFs and summarise changes" as a substitute for either path — that is a generate, it is not free, and it is not pixel-accurate.

Re-saving a PDF re-rasterises fonts and recompresses images. Almost every pixel can shift by a value or two, so every page shows as changed. Raise the tolerance until only the edits you care about remain, or compare two exports from the same tool rather than a native file against a reprint. That is a slider, not a prompt.

Credits are for the other tab

Caption burns, Hailuo takes, H3 plates, editor exports: those quote a credit figure before they charge. PDF Compare does not quote a figure because there is no charge. Mixing the two is how teams burn a model on a file job — "just screenshot the PDFs and generate a before/after." The before/after is the diff view. Screenshot if you need a still for a ticket. Do not generate.

If you needed redaction, that is a different free tool on the same shelf, also in-browser. If you needed a new page designed, that is a generate, and it will cost credits. Honesty about which object you are in is the whole decision.

FAQ

Does PDF Compare use credits or a free-generation quota?

Neither. It never spends a credit. The work never leaves your browser. Generation on Versely is a different surface and always bills.

Are my PDFs uploaded to Versely?

No. The tool uses the Canvas and File APIs on your machine. Nothing is sent to a server.

Why do identical-looking files light up as changed?

Re-save and reprint shift pixels. Raise tolerance, or compare two exports from the same app. This is a pixel diff, not a text diff.

Can I prompt a video model to animate the differences instead?

You can waste the credits. You will not get this tool's overlay. Animate a plate when the job is a plate. Compare proofs here.