II.4 Limits, plans and the daily allowance
The honest short answer
There is a free way to use Documentize and a paid one. Free use is bounded in a few specific ways. Exactly how bounded depends on the plan and on how the site is configured at the moment. So this chapter explains the kinds of limit, the mechanisms that handle them, and who states which number. It does not invent numbers.
The four kinds of limit
| Kind | What it limits | Where it comes from |
|---|---|---|
| Per-upload limits | File size, number of files, sometimes pages | The app's own FAQ and the page's messages |
| Time limit per task | How long one run may work on the free plan | Plan setting |
| Daily allowance | How many runs ("operations") per day | Plan and environment settings |
| Retention | How long results stay on the server | Fixed behaviour, about two days |
1. Per-upload limits
These are stated by each app. Examples the app chapters quote from the sites' FAQs:
- Merger and Converter: up to 10 files and about 30 MB in total per operation, as the site states.
- Compressor: a single PDF up to 32 MB per operation, as the site states.
- Other apps: see the chapter, or the numbers shown on the page.
The upload zone reports a breach with messages such as "Files upload size must be equal or less than N bytes" (with a hint to enter a URL from Google Drive, Dropbox or the public web to remove the direct-upload limit) and "The number of files can be up to N". If you hit a size limit, split the file (Splitter) or work in rounds. A free-plan run may also be capped by a PDF page limit; a paid subscription lifts that.
2. The time limit on the free plan
A free run has a time budget. If a batch does not finish inside it, the run does not fail. It delivers what it finished, shows a card titled "Free time limit reached" and keeps the rest. This is where continuations come in, below.
3. The daily allowance
Free use is counted in operations per day. The code defines an operation clearly: one processing run counts as one operation, however many files were in the batch. A batch of twenty PDFs is one operation. That makes batching worthwhile.
What the allowance is, and who gets what, is settled by plan and by environment:
- Anonymous visitors get a small daily allowance. When it runs out, the page shows "You've used all your free runs" and invites you to create an account.
- Signed-in free users get a plan-based daily allowance, which resets every day (UTC midnight, per the code). When it runs out: "You've reached today's free limit".
- Subscribers are, by default in the code, uncapped; an operator can reintroduce a cap.
- The free plan can also have a countdown, a "Full free plan - days left" banner followed by a smaller free allowance once it expires. That is information about the plan, not an error.
- The MCP channel shares the web allowance by default, and a subscription carries over.
The numbers (how many per day, how many days) are environment settings and the code only has defaults. Check the pricing page for the figures that apply to you. The book will not quote them for you.
4. Retention
Results are kept on the server for about two days, and you can delete them earlier. Details in Privacy.
Continuation: finishing a stopped batch, free
When the free time limit stops a batch, you are not charged twice. The mechanism, as the code and the troubleshooting chapter describe it:
flowchart TD
A[Big batch, free plan] --> B{Done inside the time limit?}
B -->|Yes| C[All files delivered]
B -->|No| D[Partial result delivered]
D --> E[Leftover saved: files + original options]
E --> F[Cooldown: 12 hours by default]
F --> G[Process the rest: new task, no extra operation]
G --> B
- What is kept: the files not yet processed and the original task with its options.
- How long: two days.
- The wait: 12 hours by default, set by the operator (0 means no wait).
- The price: nothing. A continuation costs no extra operation.
- Where it is remembered: in your browser, so come back with the same browser. If the id is lost, run the remaining files again.
- Where it shows: on the same app page, as "Unfinished from your last visit", with the buttons "Process the rest", "Discard" and "Later".
- Not every app can continue. Recovery and Unwatermark handle one file per run and offer none. The step-by-step is in It stopped half way.
Anonymous versus signed-in
| Anonymous | Signed in (free) | Subscriber | |
|---|---|---|---|
| Daily runs | Small allowance | Plan-based allowance | By default uncapped in the code |
| Download of a result | A visitor may be asked to sign in to collect a file after running | Normal | Normal |
| Continuations | Kept in the browser | Kept in the browser | Rarely needed; a subscription processes every page at once |
| Repo/AI apps with Apply | Not available | Apply needs a paid plan (the page says so) | Available |
Some of these are details stated on a single app's page; use the app chapter as the authority.
Habits that stretch the allowance
- Batch. One operation covers many files.
- Do the cheap checks first. A look at the document beats a wasted run.
- Choose options before pressing. A rerun costs another operation.
- Use continuations. They are free.
- Automate heavy volume. For hundreds of files, use the CLI or API (Beyond the browser).
Where the numbers live
Appendix F, Limits and plans table collects what the sites and the code state in one place. Prices are not in this book. See the pricing page.