No server-side file queue for the listed tools.
PDFTry home
Security and local processing
Security and local processing
PDFTry's main security choice is architectural: avoid uploading files for common PDF jobs. That reduces exposure, but users should still review outputs and understand browser-local limits.
No account database for normal users today.
Your browser and device memory set practical limits.
The no-upload model
The website loads code, then your selected file is opened in the browser tab. The browser performs the work locally and saves the result as a download. This avoids a PDFTry-hosted processing queue for the listed tools.
What local processing helps with
Local processing reduces the need to trust server upload handling, processing storage, retention windows, and deletion promises for common PDF tasks.
What local processing does not solve
Local processing does not make every PDF safe, guarantee perfect redaction, fix a compromised device, or replace careful review. Browser extensions, malware, screenshots, shared devices, and downloaded output handling still matter.
Browser and file limits
Very large PDFs, unusual fonts, complex forms, scans, encrypted files, or damaged documents may fail or process slowly. That is a tradeoff of doing work locally instead of sending every job to a server.
Reporting security concerns
If you find a security issue, email hello@nielskaspers.com with the affected URL, steps to reproduce, and any safe technical details. Please do not send sensitive third-party files.
Legal pages