Questions, answered plainly

No. Your browser reads the file from your disk and the tool works on it in the page—s memory. There is no upload endpoint in the site. You can verify it yourself: open the browser—s Network tab, clear it, then process a file. No request will carry the file. The how it works page explains the test step by step.

The page—s copy disappears with the tab. The only copy left is the one you downloaded, wherever your browser saves downloads. The original file on your disk is never modified in place.

No cookies, no analytics, no heatmaps, no advertising pixels. The site stores a theme choice, a local files-handled counter, pinned tools and recent tools in localStorage — all on your device. The host may keep standard technical access logs, which never contain your files. The privacy policy lists the exact keys.

A browser extension with permission to read and change pages can read what the page can read, including a file you have opened. That is true of any website and any local app. Use extensions you trust, or open the tool in a private window with extensions disabled for sensitive documents. PocketPDF itself does not load any extension.

The processing engines are open-source projects, credited on the about page. The site—s own source is not published at the moment. That is a fair thing to ask about; the honest answer is —not yet—, not a claim that it already is.

Yes, if you know the password. The Unlock PDF tool decrypts AES-256 and RC4 files locally and saves a new copy without the password prompt. It does not guess, crack or recover a password. If the password is lost, the file stays locked; that is what encryption is for.

The Protect PDF tool uses AES-256 (PDF 2.0 revision 6) by default, with RC4 128-bit available for older readers. The encryption is real and done in your browser. The weak point is the password you choose: a short, reused password is still a short, reused password. Use a long passphrase and share it through a different channel from the file.

They are requests that well-behaved PDF readers honour, not hard technical limits. A determined person with the right software can bypass them. Use encryption with a strong password when confidentiality matters; use permissions only as a polite default.

No. The signature tool embeds a drawn image on the page. It has no cryptographic identity and no tamper evidence. It is fine for a quick form or a personal letter; for contracts that need signer identity, use a qualified e-signature service.

Yes. Sanitize PDF removes document metadata such as author, title, creator and producer fields. It is not a forensic scrubber: it does not redact visible text, remove every embedded object, or guarantee that a determined analyst finds nothing. For a legal disclosure, use a dedicated redaction workflow and check the result.

Yes. The OCR tools offer 14 languages, including Urdu, Arabic, Hindi, Spanish, French, German and Chinese. Choose the language before running; the data downloads once and is cached for later runs. Accuracy depends enormously on the scan: clean digital pages are excellent, curved phone photos need corrections, and blurry handwriting is not a solved problem.

Because the video is not on someone else—s server. Video compression is heavy work wherever it happens, and your machine is doing it with one CPU rather than a data-centre rack. For short clips the wait is seconds or a minute; for a feature-length file, a desktop editor is the right tool.

There is no fixed answer because the result depends on the content. A text PDF can shrink a lot without visible damage; a photo-heavy scan has a floor before it turns to mush. The target-size tools try a range of settings and tell you what they achieved. Check the result at 100% before sending it to a client or a portal.

Not with a faithful result in the browser. That conversion needs a complete office rendering engine, which is why sites offering it run LibreOffice or Office on a server and upload your document. PocketPDF does not pretend to do it badly; the text-only PDF to Word direction is available.

Yes. The layout adapts and the PDF and image tools work comfortably. Large video jobs will drain the battery and take patience, and some browsers limit how much memory a tab may use. If a heavy job fails on a phone, try the same file on a computer before assuming the file is broken.

After a first online visit, a service worker caches the site shell and the assets of tools you have opened. Those pages then work without a connection. A tool you have never opened, and OCR language data, still need one online visit first. The offline page explains the details, and you can test it by disconnecting and reloading a tool you have used.

No imposed limit. The real ceiling is your device—s memory, the browser tab—s memory allowance and the CPU. A few gigabytes may be fine on a strong machine; a 4 GB job on a phone is not. This is the one place where upload sites genuinely win: they can throw a server farm at a huge file. Here, the file stays yours and so does the work.

A current Chrome, Edge, Firefox or Safari. The tools rely on modern browser features such as WebAssembly, Blob URLs and the File API. Very old browsers, and some locked-down corporate browsers, may block the downloads or the local workers. If a tool fails, try an up-to-date browser before assuming the site is down.

Because the file, the engine and the output are all in the same tab. A browser cannot process a 500 MB video without holding a good part of it in memory. Close other heavy tabs, use a computer for large jobs, and keep the original safe. The memory is released when the tab closes.

No. The first visit needs a connection to fetch the site, and updates need one too. After that, cached pages and used tools keep working offline until the cache is cleared. This is a normal web app with an offline shell, not an installed desktop program.

Yes. No account, card, daily limit, watermark or —2 files per hour— meter. The work runs on your hardware, so there is no server bill to recover. There is no paid tier hiding a better version.

Yes. The files you create are yours, with no attribution or license file required. Keep backups of anything important; the terms explain the common-sense side.

Please do. The contact page reaches a real inbox read by the person who builds the tools. If it can run locally, it is a candidate. If it needs a server, the answer will explain why instead of pretending otherwise.

One person in Kasur, Pakistan. The about page has the longer story, the architecture and the funding model — which is —no ads, no paid tier, no data sale—.