Limits, Free Use and Privacy
What is free in the PDF tools, file size and page limits, which plans include heavy server work, and where your file stays.
Limits, Free Use and Privacy
What is free
The PDF tools that run in the browser are free and need no account: preflight, page geometry check, adding bleed, page rotation, booklet and N-up imposition, Studio and the workflow page. Without an account, the browser limit is 200 MB and 500 pages.
What is left for paid plans?
Heavy server work and team features (shared workflow libraries) need a paid plan (Starter included); everything that runs in the browser is free. For server jobs on paid plans the targeted upper limit is higher (500 MB and 2000 pages); that limit is not open yet. Today the server takes files of at most 200 MB for everyone; confirm the current value of the page limit with support. If you reach a step that needs server work with a free account, the tool says so plainly and does not quietly do the job.
| Where | Who | Limit |
|---|---|---|
| Browser | Everyone, no account | 200 MB, 500 pages |
| Server jobs | Paid plans | today: 200 MB (target: 500 MB, 2000 pages) |
These are the general limits. Measuring total ink is narrower. A workflow with a total ink limit measures files of up to 100 pages; a longer file is not measured at all. A report's ink view measures the first 100 pages; later pages are not measured.
Where your file stays
- On your device. In the browser tools the PDF is not sent to a server; it opens in your browser and stays there.
- The file itself goes to the server only when you explicitly allow it: when you send it to a customer for approval or run a server job. In a server job the PDF is uploaded and the result files are stored on the server; only the member who started the run can download them. Sharing a report stores only a summary of the findings, not the PDF. A single-file report also carries the Document facts section (numbers, names and flags) and the names of the named colours (spot colours, varnish, registration) exactly as written in the PDF; the ink numbers per page are included too only if you tick the box. The PDF itself, a page image or a thumbnail is not stored.
- Customer approval. The comment and page notes your customer writes (including the pin positions) and the e-mail address they enter stay in the request record, are deleted when you delete your account, and are included in your data export. Only the comment and the name are written to the history, not the page notes or the e-mail. The pages are drawn in the customer's browser; the server does not read the PDF.
- Run record in this browser. After a workflow run ends, this browser keeps a short summary of it, shown under Run a workflow in Run history: the workflow's name and version, the name of the PDF you chose, how each step ended, and the names, sizes and fingerprints of the result files. It keeps the last 20 runs, only in this browser on this computer, and sends nothing anywhere. The PDF and the result files are never stored. Delete removes one run and Clear history removes them all. Details: workflows.
- PDFs you process in the free tools are not sent to AI models.
- A report share link can be opened only by signed-in members of your organization. You choose how long it lasts on the Preflight page (1, 7, 14 or 30 days). Studio uses the default of 30 days.
Your original file
When a tool changes your file, it produces a new file; the file you uploaded stays as it was. Page operations are written to the file by appending, and the output's digest shows in the receipt. If something has to be removed from the file (for example JavaScript or an embedded file), the file is rewritten from the start and the removed content really is gone; this is done only on the copy.
What the reports are worth
The tools' report is a diagnostic report; it is not a print approval. A preview is not a press proof. Your print shop's own preflight has the final say. The report is useful when talking with your print shop because it plainly says what was measured, what could not be measured and what was not changed.
Frequently asked
Why did my file come out "Review" and not "Ready"? Even an error, a warning or an info note keeps the file in Review. If a rule could not be decided, the result is Could not be evaluated (or a preliminary result). The check in the browser never gives "Ready". See the guide to reading results.
Is an RGB image an error? No. RGB becomes a finding only if you target PDF/X-1a or PDF/X-3.
Does the tool convert colours to CMYK? No. Colour conversion, transparency flattening, font embedding and trapping are the RIP's job.
Are fixes applied by themselves? No. The tools never change the inside of your file on their own, and the original is always kept.
Was this article helpful?
Related articles
Last updated on
Components, Templates and Workflows
Set up a repeating PDF job once: what a component, a template and a workflow are, how to copy and run a ready-made workflow, and why work that cannot be measured goes to a person.
Customer Approval Link
Send a PDF to your customer for approval: how to create the link, what the customer sees and can do, page notes, what happens when changes are requested, sending the corrected file as a new version, time and size limits, reminders and cancelling.