DoItAl

Your files and browser

Processing on your device.

Published calculators and file utilities perform their core work in the browser. Selecting a file gives this tab access to the file; it does not upload the contents for conversion.

What loads over the network

Your browser downloads the website and tool libraries. PDF rendering also loads a same-origin worker, fonts, and character maps. The tools then read selected files locally, compute their result, and generate a download. No remote conversion API receives your files.

What can be stored locally

Pro recipes, presets, and planning state may use local storage. Some compatible text workflows use a temporary session workspace. Tool pages identify their behavior; clearing site data removes local storage, and closing the browser session clears session state.

Why limits exist

Compressed file size is not the same as decoded memory. A 40-megapixel image needs roughly 160 MB for one RGBA pixel surface before previews and output copies. PDF jobs also have page and pixel limits. Work with smaller batches on devices with limited memory.

What local processing does not hide

Hosting requests still reach Cloudflare, and aggregate tool events can record generic actions and outcomes. Emails you send contain the message you choose to provide. Local processing is not a guarantee against browser extensions, shared-device access, or private information visible in output pixels. Read the Privacy Policy for the broader site behavior.