File security and local processing

Where your files go, what stays on your device, and what the tools can and cannot guarantee.

Your device does the processing

Selected files are read into browser memory. PDF editing runs in an isolated Web Worker; previews use the PDF.js rendering worker. These local modes make no conversion upload. The optional protected full Word pilot uses an upload to the conversion server and Adobe only after agreement; see the Privacy page.

Starting over

Start over clears the working selection and releases generated object URLs. Closing the tab ends the processing session. Downloads and the original files remain on your device until you delete them. Memory release is not a guarantee of forensic secure erasure.

Safe handling

The tools check file extensions and signatures, reject encrypted PDFs, and limit input size and page count. Embedded PDF scripts, macros, and attachments are not executed. These controls are not a malware scanner or a guarantee that a rewritten document is sanitized.

Practical limits

Each input is limited to 40 MB, with 100 MB and 30 files per job. PDF processing is limited to 200 pages. Optional English OCR is limited to 20 pages. Rendered images are capped at 16 million pixels to reduce memory pressure. Large files can still exceed a device’s capacity.

Before sharing

Check page order, orientation, text, and readability. Signatures and interactive forms may be affected. Removing pages or adding a watermark is not secure redaction or copy protection.