How processing works
Understand browser processing, server jobs, external services and file retention before you begin.
On your device
In-browser document operations use your browser’s memory and processing power. Selecting a file does not automatically mean uploading it. Keep the tab open while an operation runs. Large documents may be slow or fail on devices with limited memory. Downloaded output is saved according to your browser settings.
Server jobs
A server operation transmits its inputs to the processing backend. Inputs and outputs are temporarily stored for the job. The default job expiry is two hours, followed by periodic cleanup; deployment configuration may differ. The job response includes an expiry time when available. A completed download does not trigger immediate deletion.
External services
Some operations need external data or processing, such as exchange rates, IP lookup or AI summarisation. Browser-based controls alone do not make these operations offline. Read the operation’s description and avoid confidential input if you are unsure what is sent.
Before using an output
Keep the original. Compression can reduce image quality; conversion may change layout; merging and editing can invalidate digital signatures. Check page order, text, images, numeric assumptions and the recipient’s requirements. A tool completing successfully means the operation finished, not that the output is appropriate for every use.
Local upload checker
The upload checker reads file size and signature bytes and decodes supported images to obtain pixel dimensions. It does not upload the selected file, store a copy, inspect identity documents, count PDF pages, validate signatures or scan for malware. Its report compares only the requirements you enter.