Core concepts shared by every app
Learn one Documentize app and you have learned the shape of all of them. Part II names that shape. Seven short chapters cover the ideas that every page, in every family, relies on.
Why bother with concepts?
Because the same questions come up on every app, and the answers are the same:
- "Where do I drop my file, and what happens next?"
- "Which formats will it take, and what do I get back?"
- "What does this option really change?"
- "Why did it stop halfway?"
- "Where does my file go, and for how long?"
- "Will it read my document in the right language?"
- "Did it keep my content, or rewrite it?"
Answer them once here and the app chapters can stay short.
The seven chapters
| # | Chapter | Core idea |
|---|---|---|
| II.1 | The universal flow | Upload, options, run, result: the same four-step rhythm everywhere |
| II.2 | Formats and file types | A "document" can be text, a picture of text, or something in between; the app needs to know which |
| II.3 | Tasks, options and results | Every run is a task with a clear input, a few options and new output files |
| II.4 | Limits, plans and the daily allowance | What is counted, what can stop a run, and how a continuation finishes it |
| II.5 | Privacy and data lifecycle | Where files go, how long they stay, what AI apps read |
| II.6 | Language and localisation | Interface language is not document language |
| II.7 | The quality model | Lossless, lossy, recognised, generated: what each app does to your content |
The five-line summary
1. Every app follows Upload -> Options -> Run -> Result.
2. Your original is never modified; you receive new files.
3. Results are kept about two days; you can delete them earlier.
4. The free plan has a time limit and a daily allowance; a stopped batch can be continued.
5. Know what your app does to content: keeps it, softens it, estimates it, or writes it.
How to use this part
Read straight through the first time; it takes about thirty minutes. Afterwards, treat it as a reference. The app chapters link back here, for example from "Quality & limits", and the appendices turn these ideas into tables (format matrix, limits table).
A note on numbers
Wherever a concept needs a number, this part uses only what the code or the app's own page states, and says who states it. Allowances, sizes and prices differ by plan and by environment, so the book points to the pricing page rather than guessing.
Next
Start with the universal flow. When you finish Part II, continue to the map of how the apps relate.