Start free. Pay only when the product adds real capacity.
DocuStitch is currently focused on standard browser-based PDF workflows. Paid access is being shaped around higher limits, support, and documented processing routes, not vague privacy claims.
Standard
For routine PDF work when you want a fast browser workflow without creating an account.
- Core merge, split, compress, convert, and security tools
- 50MB standard file limit per selected file
- Browser-side processing for supported workflows
- No account required for standard tool use
- Clear route labels when a workflow behaves differently
Pro
For users who regularly need larger files, heavier batches, or priority help.
- Higher limits after capacity testing
- Priority support for workflow issues
- Reduced interruption from ads where available
- More control over OCR and export behavior
- Early access to new document workflows
Teams
For organizations that need a documented document path before using PDF tooling at work.
- Review of browser, hybrid, or server-side processing needs
- API access discussion for internal systems
- Limit planning for file size, batch size, and memory use
- Written notes for retention and deletion behavior where applicable
- Support expectations agreed before production use
A PDF plan should explain the processing route before it asks for payment.
Browser-side processing is different from a cloud upload service. It can be faster for common tasks and better aligned with sensitive document handling, but it also depends on device memory, browser limits, and the complexity of the PDF.
- Standard workflows remain free while the product matures.
- Pro limits will be published after real capacity testing.
- Team or API work needs a documented processing path first.
Current availability
If a workflow requires server infrastructure in the future, it should be labeled separately from tools that run locally in the browser.
Browser-first where supported
Many DocuStitch tools are designed to run in the current tab. That keeps routine document work closer to the user and reduces the need for a remote queue.
Limits are product behavior
File size, browser memory, OCR quality, and unsupported PDFs are real constraints. We show them plainly instead of hiding them behind a checkout page.
Paid plans need real commitments
Pro and Teams access will be sold only when the capacity, support path, and processing route are clear enough to rely on.
Pricing questions
Is DocuStitch free right now?
Yes. Standard browser-based tools are available without an account for supported workflows and published limits.
Why not list a Pro price yet?
Because paid access should match tested limits, support capacity, and real product behavior. It is better to be explicit than to sell a plan before the commitments are ready.
Does browser-side processing mean every file works?
No. Browser memory, PDF structure, OCR complexity, and the 50MB standard file limit can affect whether a document is a good fit.
Will Teams or API access make privacy guarantees?
No blanket guarantees are made on this page. Teams and API conversations should document the actual route, retention behavior, and limits for that workflow before use.
Pricing and availability may change as paid workflows are finalized | docustitch.app