Tell me what broke, what worked, or what is missing

PocketPDF is built by one person in Kasur, Pakistan. Messages, reviews and bug reports go into a private feedback log on this site — no mail app, no ticket queue, and no files uploaded.

Stored privately Read when I review the log No file uploads

Send a message

This goes to a private feedback log on this site. It is not an email draft and it is not published. If you want a reply, leave a contact; otherwise it is read-only feedback.

Your name (optional)

Contact for a reply (optional)

What is this?

Tool (optional)

Message For a broken tool: the tool name, browser, and the steps that led to it are the most useful things. Do not paste passwords, keys or a sensitive file.

Files are never uploaded. Only this message is stored.

What gets a faster reply

Name the tool, the browser, the file type and the exact step where it went wrong. A screenshot is useful; the file itself is not required.

What is stored

The message type, optional name and contact, the tool, a review rating, your message, the page address, browser user-agent, viewport, language and the time. Not your files and not your IP address.

Security reports

Choose —Security report—. Please don—t include live credentials or a file you do not have permission to share. There is a disclosure policy.

Password recovery

There is no recovery path for a PDF password you set here. The encryption is real; nobody — including this site — can open the file without the password.

Something broke

A crash, a blank result, a download that never arrives. These are the most useful messages and usually the quickest to fix.

A tool is missing

If it can run in a browser without uploading files, it is a candidate. If it needs a server, you—ll get an honest explanation rather than a promise.

Privacy or security

Questions about what the site can see, how encryption works, or what a browser extension could access are welcome. The answer will be specific.

What happens after you send

It lands in a private log.
Not a ticketing system, not a chatbot, and not a public review wall. It is a text record on the site.
It gets read when the log is reviewed.
If you left a contact, that is where a reply can go. If you did not, the message is still useful as a report.
You get an answer, or an honest —not yet—.
Not every request fits the no-upload architecture. When one doesn—t, the reason will be explained instead of ignored.

Before you write

The FAQ covers the common questions — offline use, file size, password-protected PDFs, OCR languages and commercial use. The privacy policy explains exactly what is and is not stored. If your question is already answered there, it will be a faster read than waiting for a reply.