PDF Repair in the browser is not a generate
/free-tools/pdf-repair never spends a credit. Do not pay a model to do an in-browser file job.
/free-tools/pdf-repair never spends a credit. Do not pay a model to do an in-browser file job.
PDF Repair loads the file and writes it back out, which rebuilds the cross-reference table and object graph. That repairs a class of structural corruption — a truncated xref, a lingering incremental update, a missing trailer. It does not reconstruct damaged content streams: a page whose operators are already garbage will still be garbage, just inside a valid file. It runs in your browser. Nothing is uploaded. Nothing is sent to a model. There is no account gate and no generation meter.
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 "this PDF will not open." Do not prompt a video or image model to "fix this PDF."
The rebuild never leaves the machine
The file you choose is read into memory locally, rebuilt there, and offered back as a download (-rebuilt.pdf). 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 Repair 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 "repaired file." You will spend a clip rate to invent a visualisation of a document. You will not get a rebuilt xref. You will get a generate. The repair already writes a valid container. That is the artefact.
Structure, not the drawing
This is a container fix. A file that will not open at all is in range. A file that opens with a black or garbled page is not. Rewriting the xref cannot invent missing operators on a page whose content stream is already damaged.
The output is not byte-for-byte the same as the input, and it should not be. Incremental updates are folded in, object numbers may change, and unused objects can be dropped. The pages you can already see should look the same; the bytes will not match a hash of the original, which is the point of a rebuild.
If you needed a visual compare of two proofs, that is PDF Compare on the same shelf — also in-browser, also zero credits, a pixel diff not a text diff. If you needed redaction, that is a different free tool. If you needed a new page designed, that is a generate, and it will cost credits.
Credits are for the other tab
Caption burns, Hailuo takes, Ideogram plates, editor exports: those quote a credit figure before they charge. PDF Repair 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 broken PDF and generate a clean one." The clean one is the rebuild. Screenshot if you need a still for a ticket. Do not generate.
Honesty about which object you are in is the whole decision. A structural rebuild is a browser utility. A new page is a model. Do not pay a model to do an in-browser file job.
FAQ
Does PDF Repair 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.
Will this recover a blank or garbled page?
No. If the content stream on that page is already damaged, rewriting the xref cannot invent the missing operators. A file that will not open at all is in range; a file that opens with a black page is not.
Can I prompt a model to reconstruct the missing pages instead?
You can waste the credits. You will not get this tool's rebuilt object graph. Reconstruct a page when the job is a generate. Repair the container here.