Implementation architecture

A transformation platform packaged as a static website.

UsefulUtility separates a searchable application shell from versioned deterministic processing engines. The same engine packages can be embedded across the ZenBinary suite.

Static interface

Next.js App Router, React, TypeScript and Tailwind compile to a hostable static export.

Job runtime

Comlink brokers typed requests to disposable Web Workers; FFmpeg uses its own local worker.

Engine packs

Canvas, Resvg WASM, pdf-lib, zip.js, SheetJS, Ajv, Three.js and FFmpeg load by tool category.

Local workspace

OPFS stores larger outputs; Dexie stores history, recipes and IndexedDB fallbacks.

Offline shell

Workbox precaches the export and caches heavy engine assets on first use.

Static deployment

No API routes, Server Actions, upload handlers or conversion services are included.

Processing path

Validate

Check file signatures, sizes, options and current browser capabilities.

Dispatch

Lazy-load the relevant engine and transfer input to a local worker.

Transform

Run the exact operation with progress, cancellation and bounded local resources.

Persist

Return a Blob, retain it locally when possible, and offer explicit export actions.

Intentionally included

Production foundations, image and PDF operations, archives, structured data and spreadsheets, developer utilities, calculators, common media transcoding, mesh inspection/conversion, history, recipes, real toolchains, PWA support, deployment headers and automated tests.

Intentionally not misrepresented

High-fidelity Office rendering, arbitrary proprietary codecs, parametric CAD round trips and commercial PDF engines require separate licensing, much larger binaries or a product-specific integration. Extension boundaries are documented without presenting those capabilities as finished.