Local PDF processing
A clear explanation of what runs in the browser and which limits are intentionally kept.
Why this approach
The site focuses on operations that can run directly in the browser to reduce unnecessary dependencies and avoidable risk.
What it changes
The public experience now matches the actual product: supported PDF actions, direct pages and fewer moving parts.
What was removed
Unused proxies, exposed client-side keys and pages promising unsupported features were removed from the public site.