Workspace · nothing uploaded, nothing saved
Load a document once, stack up the jobs — rotate, sign, number, compress — and download the result at the end. The file is held in this tab's memory and never written to disk, so nothing is left behind when you close it.
Steps run top to bottom. Compress is usually last — there is no point shrinking a file and then stamping a signature onto it.
Done — and nothing was uploaded or saved. Everything happened in this tab's memory.
Kagaz is free and open source, made by Amit Jena in India. It has no server, no accounts and no analytics — so I have no idea you were here, which is the idea.
Each Kagaz tool does one job and hands you a file. That is fine when you need one thing, and tedious when you need four — photograph a form, sign it, number the pages, shrink it for an upload limit. On a laptop that means four trips through the downloads folder. On a phone it is worse.
Here the document is loaded once and every step runs against the result of the last one, in memory, in this tab. You download at the end.
There is an easier way to build this: save the file to browser storage between tools and pick it up on the next page. It works, and it means your document gets written to your disk by a website — which for a passport scan or a medical letter is a real change, however local.
So the workspace keeps everything in memory instead. Close the tab and it is gone, with nothing to clear out afterwards.
Redaction and visual page organising stay on their own pages, because both need you to point at specific parts of specific pages. Squeezing that into a step card would make both worse. Run the workspace first, then take the result to those tools — or the other way round.
No. There is no server. Open the Network tab and run a chain — nothing goes out.
Yes. Drop images instead of a PDF and they are assembled into one first. To use your camera, start at Scan to PDF and bring the result here.
The run stops at that step and tells you which one, with the document unchanged. Nothing is half-applied.
Every intermediate result is held in memory, so a chain uses more than a single tool would. A laptop copes with a few hundred megabytes; a phone will want to stay well under.