How it works

This editor runs in your browser and processes PDFs on-device. Your files are loaded, edited, and exported locally, so your document content stays on your machine by default.

Local-only processing

  • You choose a local PDF file and the browser reads it directly on your device.
  • PDF bytes are parsed and rendered in the browser.
  • Text edits, page operations, and signatures are applied on-device.
  • Export creates the final PDF locally before download.
  • No background upload is required for core editing workflows.

How many tools usually work

  • Server-first model: file is uploaded to a backend where processing happens remotely.
  • Cloud workflow model: file is synced to cloud storage, then edited through cloud services.
  • Hybrid model: some actions stay local, but OCR, conversion, or signing calls remote APIs.
  • These approaches can be valid for collaboration and heavy compute, but they usually mean document data is transmitted or stored outside your device.

Local-first vs cloud processing

CategoryLocal-first (this app)Typical cloud/server flow
Document transferStays on your deviceUsually uploaded for processing
Core editsBrowser runtime onlyOften executed on backend services
Failure modeMostly local device/browser constraintsMay depend on API/cloud availability
Data footprintNo server copy for normal editsTemporary or stored server-side copies are common

Why local-first matters

  • Privacy: document contents do not need to leave your machine for normal editing.
  • Control: you keep the original and edited files in your own local environment.
  • Predictability: no dependency on third-party file processing availability for core edits.
  • Simpler trust boundary: for core editor usage, processing stays inside your browser session.

How files are protected

  • Files are never uploaded for editing or conversion.
  • No cloud document processing is used by this app.
  • Network guardrails block non-local runtime calls in production by default.
  • Billing and entitlement checks do not include document content.

What leaves your computer

  • Only billing-related metadata when you explicitly open hosted payment/portal pages.
  • No PDF contents, text spans, highlights, or signatures.
  • If you open external links (for example, feedback forms), those pages follow their own privacy policies.