Browser and device compatibility
The core randomizers need a secure modern browser. Optional export, local-image, sharing, and offline capabilities are detected separately and fail honestly when unavailable.
Core requirement
All random decisions require crypto.getRandomValues() in a secure context. Current Chrome, Edge, Firefox, and Safari releases normally provide it over HTTPS. The site does not silently substitute a weaker source.
Saving and migration
Workspaces and small tool histories use versioned browser storage. Private or restricted modes may clear or reject storage. Import/export remains the portable backup path, and imports are fully validated before replacing current data.
Clipboard, files, PNG, and print
Clipboard, native sharing, canvas PNG, file pickers, and printing depend on browser and permission support. Each is an enhancement: text/JSON/CSV downloads or on-screen results remain available when a richer path is blocked.
Local images
Image tools decode selected files on this device, enforce file and pixel budgets, and release object URLs. Unsupported image formats, oversized projects, or failed decodes are reported per item and are never uploaded for server fallback.
Offline behavior
The installable app caches the public shell and previously visited same-origin pages. It never caches user-entered names, image blobs, results, API traffic, analytics requests, or URL fragments. Open a tool online once before relying on it offline.
Product and methodology review: