Inside Fixora

How Fixora processes data

A transparent explanation of Fixora local file and text processing.

A simple file workflow

File tools follow this sequence. Live text and numeric tools use their own input controls.

  1. 1

    Choose your input

    Choose a supported file from your device.

  2. 2

    Process in your browser

    File tools use local browser processors. Check the individual tool for its limits.

  3. 3

    Review and download

    Inspect the result before saving it to your device.

Inside your browser

React tool interfaces read the values you enter or files you select. Text and structured data use bundled JavaScript processors. Image tools use browser decoding, Canvas, Blob, and download APIs. Meeting times use the browser’s Intl time-zone database; the calendar file is created locally. Some text/data tools use a local Web Worker.

What is not sent

Tool files, filenames, tool inputs, extracted content, results, and generated downloads stay in your browser. Separately, details you explicitly submit through /contact/ are sent to the server and stored in a private database. Fixora does not require an account.

Memory and cleanup

Input lives in the page memory while the tab is open. Generated object URLs are released when replaced or reset. A loaded local processor may remain in the tab until the page closes. Reloading the page clears tool state. Your browser may retain ordinary cache and download history under its own settings.

Practical limits

Local processing consumes your device memory and CPU. Safety caps reduce accidental overload but cannot predict every device limit. Close other heavy tabs and work with smaller batches if the browser becomes slow.

Contact processing

The contact form uses Cloudflare Turnstile verification and a narrowly routed Pages Function to store correspondence in private Cloudflare D1. It does not upload tool files or read tool workspaces. See /privacy/ for contact retention and deletion.

Keep your source files private.

If you report a problem, share the tool name and a nonsensitive example, not confidential files or secrets.

Help & contact