How this works

Not Only PDF is a set of file tools that run inside your browser. Today they work on PDFs; the name is a promise about where that goes, not a claim about what is here yet. When you open a file, it is read by code running on your own machine. It is never sent anywhere, because there is nowhere to send it: this is a static site with no server that could receive a file.

this computer

your filestays here
Not Only PDFWebAssembly
the resultyou save it

everywhere else

nothing

no upload, no account, no record of what you open

Nothing crosses the dashed line. The page itself is downloaded from a server, like any page — that happens before you choose a file, and nothing is requested afterwards.

How you can check any of this

Open your browser's developer tools, go to the network tab, and use the tools. After the page and its engines have loaded, you will see no further requests — not while a file is open, not when one finishes. The same thing is asserted on every commit, in three browsers, by a test that reads the web server's own log rather than the browser's report of it.

The code is public, and so is the reasoning behind it: the architecture decisions are written down, including the ones that turned out to be wrong.

What is finished and what is not

Every tool linked from the front page works today. A tool is only linked once its page ships — there is no sign-up to wait on and nothing is announced before it works.

Not Only PDF is being built in the open and is not finished. Redaction is still to come, and it is the one this project is most careful about. What is here has the safety work around it done: every operation checks its own output before handing it to you, and refuses it rather than give you a document that is quietly wrong.