ZANCTA

/docs

ZANCTA documentation

Everything you need to know: what a tool accepts, what it produces, and how supported local processing behaves — written for the product you can use today.

01

Tool collection

The tool collection is the current catalog. PDF workflows cover merge, split, compression, page rendering, image-to-PDF, and embedded-text extraction. Image workflows cover compression, conversion, resizing, metadata cleaning, and local English OCR.

02

Inputs and limits

Every tool page shows its accepted file type, maximum size, and batch limit. Most local PDF and image workflows use a 50 MB per-file boundary. OCR uses a 20 MB image boundary and supports JPG, PNG, and WebP. The displayed tool limit always takes precedence.

03

Processing and output

Implemented local tools process selected file bytes in the browser and generate outputs on-device. A tool may provide a download, copy action, preview, or all three depending on its purpose. Progress is tied to reported engine work where that is available.

04

OCR and PDF text

Image OCR uses bundled English assets in a browser Worker. PDF Text Extractor reads embedded text page by page from text-native PDFs. It does not turn scanned PDFs into text and reports an honest no-text state for image-only documents.

05

Accounts and subscriptions

Local tool use is available without an account. Accounts support authentication and entitlement records. Premium and payment behavior are presented on Pricing only when provider configuration makes those actions available.

06

Known limitations

Browser APIs, memory limits, protected PDFs, malformed files, and unsupported formats can prevent completion. Background removal is deferred while local model licensing is evaluated. See Help and FAQ for practical recovery guidance.