About

Tools that do not ask for your document

Most document tools ask you to upload a file to a company you have never heard of, then promise to delete it. This one cannot ask, because there is nowhere to send it.

Why it is built this way

Browsers can now do the work that used to need a server: read a PDF, draw its pages, write a new file. Once that is true, uploading a contract, a bank statement or a passport scan to a stranger's server is a risk with nothing to buy. So the tools here run in your browser, and the site is a set of static files with no backend to receive anything.

Why you should not simply believe that

“Your files never leave your browser” is a sentence anyone can write, and plenty of sites write it while uploading. Do not take our word for it: open your browser's network panel while you use a tool, or put the device in airplane mode after the page has loaded and watch the tool keep working. The claim is checkable, which is the only kind worth making.

You will see requests that are not this site's own code, and they go to two places, neither of which is sent your file: our page-view counter at analytics.pagefabrica.com, which receives the address of the page, and — only if you open the Pro door on an OCR tool — Hugging Face's servers, from which this browser downloads the Deep reader's model once. Both are named here because the front page counts them, rather than being quietly left out of a number that would otherwise read better. What each receives is set out in full.

How it is paid for

The site is intended to be funded by advertising placed away from the tools and never between a control and its result. The current ad-unit identifiers are empty, so the marked surfaces are hidden and no advertising library is requested. There is no paid tier today. The Pro door on the OCR tools shows a price and measures whether anybody would pay it; everything behind the door is free during the preview, with no card and no account. Nothing about your document can be used to select an advertisement — the document is never seen by this site, let alone by an advertiser.

The rule about what gets built

Nothing ships here until it can prove its own result. That rule delayed password protection for a long time, because the honest answer to “is the encryption sound?” was “nobody here has read the code that would do it”.

The protection path is measured rather than trusted: a fixture document declares AES-128 revision 4 protection, sampled text does not remain in clear bytes, a separate reader refuses the no-password open, and the same reader opens it with the supplied password. Those assertions run with the tenant tests and browser workflow.

The limit is stated instead of hidden. This is AES-128, not AES-256, and weak passwords remain vulnerable to guessing. The tool refuses a few plainly weak shapes, asks for a long passphrase and re-opens every finished file before offering it.

Editorial policy

This is how the pages on Steady PDF are kept honest. It describes how the pages are written and the checks that are run on them, not a promise about any one reader's experience.

How a tool is checked. The tools that rewrite a document, which are redaction, password protection and removal, editing, signing, form filling and metadata removal, open their own finished file again before offering a download and compare it with what you asked for. How it works says what is checked and where each method stops.

How a claim is tied to evidence. A sentence that says what a tool does, how much it downloads, or what it never sends is recorded with the test, measurement or receipt that supports it. The claims check run on the built site refuses a recorded claim whose sentence is no longer on the page it was recorded for, so a claim cannot quietly be reworded away from its evidence.

How limits are written. Tool pages state their limits, such as memory on a phone, a missing text layer in a scan, or a browser that cannot do the work. A limit is written next to the thing it limits, and a feature that is only in preview is called a preview.

Corrections. If a page is wrong, write to support@steadypdf.com and name the page. A claim that turns out to be wrong is corrected or removed, and the contact page says what to include.