Vision — why Documentize
It is 5 p.m. Your manager forwards a 90-page market study with one line: "Thoughts by tomorrow?" You will not read 90 pages tonight. Then the client asks for your own 90-page quarterly report as well, and the mail system bounces it: too big. It has a cover sheet you never meant to send and two blank pages from the exporter. Your evening is now a scavenger hunt through a desktop editor, three free sites in three browser tabs, and a forum thread from 2019.
Nothing about this is difficult. That is exactly what makes it infuriating. Document chores are small, boring, urgent and always arrive together.
This book is the way out. It takes the website you may already know, products.documentize.app and products.documentize.ai, and turns it into a toolbox you can use with confidence.
The turn: small apps, big chains
Documentize does not try to be one giant editor. Each page does one job: Merger merges, Compressor shrinks, Ask PDF answers questions about your document. Every result is an ordinary file, so it goes straight into the next app. Your original is never touched.
One job is useful. A chain of jobs is where it gets good. Here is a real one, from the recipe Phone photos to a clean searchable PDF:
- Before: a dozen phone photos of a lease, some crooked, two lying on their side, each 4 MB.
- Chain: Merger → Rotation → Deskew → Searchable → Compressor.
- After: one straight, upright PDF you can search with Ctrl+F and email.
Five apps, no installation, no manual.
What you will be able to do
Pick any of these; each is a recipe with the starting state, the chain, the options and a check at the end:
- Send a big report by email: cut the pages nobody needs, tidy the file, shrink only if you still have to.
- Turn phone photos into a searchable PDF.
- Understand a long document fast: from "a 120-page report landed in my inbox" to a gist, a one-page reference and answers with proof, in about 20 minutes.
- Assemble one submission pack from many files.
- Print a folded booklet.
- Share only part of a document.
Twenty-odd recipes in all, in Part XII.
The promise, and its fine print
This book is honest, and that is a feature. Where the product has a gap, the book says so: there is no PDF Redactor and no Compare PDFs app, and the Parser does not give you tables. Where an app is lossy (Compressor softens pictures on purpose), the chapter tells you before you click. Where AI writes a draft, it is called a draft.
Three ways to read it
| You are... | Start with | Why |
|---|---|---|
| In a hurry, with a task | The goal finder, then a recipe | Goal first, tool second |
| Curious about every tool | Part II, then your family of apps | Learn the shared shape once, then every app is familiar |
| Planning to automate | Beyond the browser | The same engine runs as CLI plugins, an MCP server and an API |
Details are in How to read this book.
What this part covers
| Chapter | The question it answers | Read it if you want to know... |
|---|---|---|
| The problem | Why is "just handle this PDF" never just one thing? | Why documents turn into a pile of small chores |
| One app, one job | What is the Documentize idea? | Why a shelf of small tools beats one giant editor |
| Two sites, one family | Where do I go? | Which of the two sites to open for your task |
| How to read this book | Where do I start? | Three reading paths, and how every page is built |
| The portfolio at a glance | What is actually on the shelf? | Every app on one page, grouped by family, with links |
Five short chapters, about fifteen minutes. In a hurry? Read only Two sites, one family and open the portfolio.
Next
Start with the chore list that makes the whole idea necessary: The problem: documents are a pile of small chores. After Part I, Part II explains the seven ideas every app shares.