Tools
FAQ

Frequently asked questions

Everything people ask before they trust a website with a document. If your question is not here, write to us.

Privacy and security

Are my files uploaded to your server?

No. There is no upload endpoint on this site. Every tool is JavaScript running in your own browser tab, reading the file through the browser's local file API. You can confirm this yourself: open your browser's developer tools, switch to the Network tab, and process a file — you will see no request carrying its contents.

Can I use the tools offline?

Yes. All the libraries this site needs are bundled with it rather than loaded from a third-party CDN, so once a page has loaded it keeps working without a connection. This is also why the site behaves the same on a slow hotel Wi-Fi as on fibre.

Do you keep a copy of my document anywhere?

No copy exists to keep. The file is held in your browser's memory while you work, and discarded when you close the tab or reload the page. We could not retrieve a document for you even if you asked, because we never receive it.

Using the tools

What is the largest file I can process?

There is no quota imposed by us. The real ceiling is the memory available to your browser tab, so a desktop with 16 GB of RAM handles far more than a phone. Files in the low hundreds of megabytes are usually fine on a laptop; on mobile, stay well below that.

Does it work on a phone or tablet?

Yes. The layout adapts to small screens and the tools run in mobile Safari, Chrome and Firefox. Heavy operations — rendering hundreds of pages to images, for instance — are slower on a phone and more likely to run out of memory.

Which browsers are supported?

Any current version of Chrome, Edge, Firefox or Safari. The tools rely on modern browser APIs, so Internet Explorer is not supported, and very old Android browsers may struggle with the heavier converters.

Quality and limitations

Why did compression hardly reduce my file size?

Because compression works by re-encoding the images stored inside the PDF. A document that is mostly text has very little image data to re-encode, so the file barely moves. A scanned document, which is essentially a stack of photographs, can shrink dramatically.

Why is the Word-to-PDF output not selectable?

Because there is no Office engine on the server — that is the trade-off that keeps the conversion local. The browser parses the .docx into HTML and then rasterises it, so the pages become images. The layout is preserved; the text is not machine-readable.

Is the output watermarked?

Never. Nothing is stamped on your document and there is no paid tier that removes a stamp. The only watermark a file can have is one you add yourself with the watermark tool.

The site itself

How is this site funded, if everything is free?

By display advertising. It is the model that lets the tools stay free and unlimited without charging you, requiring an account, or inspecting the documents you process. Advertisers never see your files — they cannot, since the files never reach a server.

Do you use cookies?

Yes: one to remember your language, and advertising cookies set by third-party vendors including Google. You can block or delete them in your browser settings and the tools will still work. The privacy policy explains this in full.

Can I suggest a tool, or report a bug?

Please do — it is a one-person project, so the feedback loop is short. Bug reports that mention the tool, your browser and the file type are the fastest to fix. Requests that would need server-side processing have to be declined, since that would break the site's only real promise.

Get in touch

Email reaches a real person, usually within two working days. Bug reports with the browser and file type included get fixed fastest.