Is Smallpdf Safe? What Its Policies Say

Yes, Smallpdf is safe for ordinary documents such as public forms, slides, manuals and anything you would be comfortable emailing. It is run by Smallpdf AG, a company with a registered address in Zurich, Switzerland, and it publishes a privacy notice, terms and a safety page. The catch is the one every online PDF site shares: your file is uploaded to someone else's server. The more useful question is whether you are comfortable with that upload and whether Smallpdf's own pages agree with each other. Everything below comes from Smallpdf's privacy notice, terms and its Is Smallpdf Safe blog post, all read on 2026-11-05, and we flag where they differ or say nothing.

One hour for most uploads, according to Smallpdf, but its pages word this differently. The blog post says files from free tool use are deleted after one hour. The privacy notice says that if you use a User Account, files are deleted within one hour unless you save them to your file storage. For visitors without an account or not logged in, the notice only says it will generally aim to delete files within a reasonable period after they were last opened, and that period is extended every time you reopen the file. That is not a fixed number. Saved files are a separate case, covered next. If a file matters, delete it yourself and do not rely on the timer.

The two pages give different answers for files you delete from account storage. The blog post says that if you delete a file from your online storage, it is removed from the servers within an hour, and that no part of the file is kept afterwards. The privacy notice says that when you choose to delete saved files, it generally deletes them within 14 days. We cannot tell from the pages which one governs, and Smallpdf does not explain the gap. The privacy notice is the legal document, so plan around 14 days if you use cloud storage. If you never save files to an account, this does not apply to you.

The blog says servers are in Ireland and that only you can see your documents, but the privacy notice is less absolute. The notice says files are processed with Hetzner on servers in the European Union, without permanent storage, and that Cloudflare may handle data on servers in the United States or in Europe, chosen near the user. It also says authorized Smallpdf staff and service provider staff have access to personal data. The terms say Smallpdf may access, view or listen to your content to answer support requests, address fraud or technical issues, improve its services and enforce its terms. So the blog's claim that employees cannot access documents is stronger than what the terms allow.

Smallpdf says transfers are encrypted, and the blog says it is ISO 27001 certified. The privacy notice says all communication and file transfers to and from its servers are encrypted with TLS. The blog adds 256-bit TLS and cites ISO/IEC 27001:2013. ISO 27001 certifies a company's security management process, not any single file, and the blog does not name the auditor or give a certificate number. Neither the privacy notice, the terms nor the blog says whether files are encrypted at rest on the servers. TLS protects a file in motion only. That is a real gap if your concern is what happens to a file while it waits on a server.

Several details are not published on the pages we read. The privacy notice did not mention backups, so we cannot say whether copies outlive the deletion windows. It gave no single retention period for IP addresses or logs; the only fixed figures we found were 12 months for consent logs and 180 days for the Facebook Pixel. The terms say the services are provided AS-IS and disclaim any warranty that they will be secure or error-free, and they exclude liability for loss of data, with carve-outs for gross negligence. Also note the blog's safety claims are marketing copy from the vendor, and the terms are the document that carries legal weight.

We read the source for the PDF tools. Merge PDF, Compress PDF and Split PDF run in your browser, and their stores contain no fetch calls. The only outbound signal we found is a tool_start analytics event carrying the tool name. One detail from the Compress PDF code: it only recompresses embedded JPEG images, at quality 0.4, 0.6 or 0.75 for low, medium and high, and it also caps image size at 1200, 1600 or 2000 pixels. It skips CMYK JPEGs rather than risk wrong colors, so a text-only PDF will barely shrink, and the code comments call that an honest result. Protect PDF applies AES-256 with qpdf compiled to WASM in a web worker. The tradeoff is scope, and we verified only these tools.