Questions, feedback, bug reports, or privacy requests — here is how to reach us and what to expect.
SimpleSignPDF is a small independent project rather than a company with a support department, so email is the only support channel and replies come from a person rather than a ticketing system. That means responses are considered but not instant. Before writing in, it is worth checking the troubleshooting section further down this page, because the large majority of reports fall into one of a handful of well-understood causes that you can resolve yourself in under a minute.
For technical issues, feature requests, and general questions.
support@simplesignpdf.comTypical response: within 24–48 hours on business days
For GDPR requests, data inquiries, and legal notices.
support@simplesignpdf.comSee our Privacy Policy for data rights
Because SimpleSignPDF runs entirely inside your browser, almost every problem is one of these five. Each has a fix you can apply immediately.
Why it happens: The most common cause is that the file is password-protected or has editing restrictions applied. An encrypted PDF cannot be decrypted and modified in the browser without the password.
How to fix it: Open the file in your normal PDF reader, confirm whether it prompts for a password, and if so re-save an unprotected copy (in most readers: open with the password, then Print → Save as PDF). Also confirm the file really is a PDF rather than a renamed image or Word document.
Why it happens: This nearly always comes from uploading a photograph of a signature written on paper. Camera images carry shadows and an off-white background that reads as grey once placed on a white page.
How to fix it: Use the Upload tab with background removal enabled, which strips near-white pixels to transparency. Better still, use the Draw tab with a trackpad or touchscreen, or the Type tab, both of which produce a clean transparent signature with no background at all.
Why it happens: Usually the recipient opened a stale copy — the original file rather than the downloaded signed version — or is previewing it in an email client whose built-in viewer renders incompletely.
How to fix it: Confirm you are sending the file whose name ends in _Signed.pdf. Ask the recipient to download the attachment and open it in a proper PDF reader rather than an inline email preview. Opening your own downloaded copy before sending is a worthwhile habit.
Why it happens: Almost always the signature was placed on a different page than intended, or the document was scrolled between placing and downloading.
How to fix it: Use the page thumbnail rail to confirm which page each item sits on before downloading. Select an item and use the arrow keys to nudge it precisely, holding Shift for larger steps.
Why it happens: Either no signature or text has been placed yet — the button stays disabled until the document has at least one annotation — or a browser extension is blocking the generated file.
How to fix it: Check that at least one item appears on the document. If the button is active but nothing downloads, try a private/incognito window, which disables most extensions, and check your browser has not silently blocked the download.
Because documents never reach our servers, we have no logs of your session and cannot reproduce a problem from our side. A useful report therefore needs to carry its own context. Please include your browser and version, your operating system, whether the document is single or multi-page, roughly how large the file is, the exact steps that led to the problem, and any message shown in the browser console if you know how to open it.
Please do not attach the document itself. It is almost always a contract or other private paperwork, and we do not want a copy of it. If the problem appears specific to one file, try to reproduce it with a document containing no sensitive information and send that instead.
Questions about legal validity, document types, and workflow are covered in more depth here:
Resize using the green corner handles. To remove it, click to select then press Delete, and create a fresh signature with "New Signature". The "Type" option often gives cleaner results for precise placement.
Check the PDF isn't password-protected (encrypted PDFs can't be modified client-side). Try Chrome or Firefox for best compatibility. Very large files (50MB+) may need compressing first.
Yes — email support@simplesignpdf.com with as much technical detail as possible (browser, OS, steps to reproduce). We investigate all security reports promptly.
Use the 'Clear All' option in the signatures panel, or clear your browser's local storage in your browser settings (Settings → Privacy → Clear browsing data → Cookies and site data).
SimpleSignPDF doesn't store your documents or personal data on our servers — there's nothing to delete. Your signatures live in your browser's local storage, on your device only.