fileformer
search⌘KtranslateENexpand_moreupload_fileConvert
Converters8 file families · 44 direct conversions
What changes in a conversionarrow_forward
Monitor running on this page

How file processing works.

Tools run in your browser tab, on your processor, from opening a file to saving the result. The panel on the right is a live monitor of this page's real network activity. Convert a file and watch it stay on your device.

laptop_macEvery converter, compressor and editor on the site works in the tab, on your device.
downloadSome tools fetch code or models from public CDNs when needed. That is code arriving at your browser; the audit below names each source.
keyboardTwo tools send what you type by design: DNS Lookup (the domain) and the password breach check (5 hash characters). Both say so on the page.
lanNetwork · this page, live
upload_fileConvert my filephotoSampleboltTest request
atrequesttypedownbody up
0.06sunpkg.com › react-dom.production.min.jsscript0 B0 B
0.06sunpkg.com › react.production.min.jsscript0 B0 B
0.04sfonts.googleapis.com › css2linkcache0 B
0.04sfonts.googleapis.com › css2linkcache0 B
sample-photo.png → sample-photo.jpg in 302 ms. No network requests in that window.
requests since load 13during conversion 0bytes sent in bodies 0 B
~/inside-the-tab

Where your file was, step by step.

The run above went through these stages. Each one names the browser object holding your data and how long it took on this device. Images are re-encoded to JPEG; anything else is compressed to .gz, so every file type has a real result.

Running the sample conversion in this tab…
folder_open<1 ms
You picked itFile (a reference, 1.06 MB)The browser hands the page a handle to the file on disk. Nothing is read yet.
memory253 ms
Read into memoryArrayBuffer · 1,063,911 bytesThe bytes are copied into this tab’s memory, like opening a file in any app.
fingerprint3 ms
FingerprintedSHA-256 b9d13f149f3b0662…A hash computed here, so you can match it against the file on your disk (shasum -a 256).
image31 ms
DecodedImageBitmap → canvas 1600×1200The browser’s own image decoder turned the bytes into pixels on the GPU or CPU.
download15 ms
Result createdBlob · blob:http://127.0.0.1:9777/a63f2…The output exists only as a blob: URL owned by this tab. Saving it is your browser’s normal download.
1.06 MB in, 285.6 KB out as JPEG at quality 85, 302 ms in total. SHA-256 of the input: b9d13f149f3b06620de648921e581c909bfbb51a966f67f1d3c915be46ce808e. Close the tab and every one of these objects is gone.downloadsample-photo.jpg
~/every-outside-address

Not everything is local. Here is exactly what isn't.

This page fetches the source of 18 FileFormer pages plus the shared runtime and lists every outside address their code can contact. Citation links in a page's sources are counted separately: they are only followed if you click them. The fetches it makes to do this appear in the network panel above.

travel_exploreRun the audit
addresswhy it's contactedwhat it receivesfound in · run the audit
fonts.googleapis.comfonts.gstatic.comfontsTypeface stylesheets (Geist, Material Symbols); The font files themselvesYour IP address and the page address as referrer. No file content.-
unpkg.comruntimeReact, loaded by the shared page runtimeYour IP address. No file content.-
cdn.jsdelivr.netdecoderLibraries loaded on demand: HEIC decoder (libheif), QR encoder, transformers.jsYour IP address. Code comes down; nothing of yours goes up.-
huggingface.comodelMODNet weights for the AI cutout, only after you click LoadYour IP address. The image stays in the tab.-
cloudflare-dns.comdns.googledns.quad9.netyour inputDNS lookups over HTTPS (first one, then the others as fallbacks)The domain name and record type you typed.-
api.pwnedpasswords.comyour inputBreach check, only when you click itThe first 5 hex characters of the password’s SHA-1 (k-anonymity); never the password.-
The table shows what we know each address is for. Run the audit to have this page read the code and say where each one appears.
~/what-a-page-cannot-prove

What the monitor above can and can't see.

A page can only watch itself. These are the mechanisms it relies on, checked in this browser, and the blind spots where you need your browser's own tools or a network capture.

timerResource TimingEvery request the page itself makes is reported here with timing and size, including images, scripts and fonts.PerformanceObserver: active
codeRequest hooksfetch, XMLHttpRequest, sendBeacon and WebSocket are wrapped so the body size of anything sent is counted before it leaves.fetch ✓ · xhr ✓ · beacon ✓ · websocket ✓
dnsCross-origin sizesFor other sites, browsers hide sizes unless the server allows it (Timing-Allow-Origin), so some rows show 0 or “cache”. The request is still listed.shown as 0 B when hidden
engineeringService workersA service worker can make its own requests outside this page’s view. FileFormer pages don’t register one.no service worker controls this page
extensionExtensions and other tabsBrowser extensions and other tabs have their own network activity; this page can’t see or prevent it. Devtools shows extension requests.outside this page
web_assetOther frames and workersRequests from iframes or web workers are not in this page’s timing list. None of the audited tools uses them for networking.check with devtools
routerBelow the browserThe operating system, VPN or proxy see connections, not contents (HTTPS). A packet capture is the final word.use Wireshark or mitmproxy
verifiedSame file, same hashCompare the SHA-256 shown after a run with one computed on your own machine to confirm the page read exactly your file.macOS/Linux: shasum -a 256 file · Windows: certutil -hashfile file SHA256
infoFileFormer has no formal attestations such as HIPAA or SOC 2. Local processing removes the upload, but your device, browser and extensions are still part of the path; use your own judgement for regulated work.
~/verify

Don't take our word for it.

Your browser can show you every request a page makes. The monitor above uses the same timing data devtools does, but devtools also sees other frames, workers and extensions. Watch it while you convert a file in any tool.

desktop_windowsWindows / LinuxF12
laptop_macmacOS⌘⌥I
webAny browserRight-clickInspect
1
Open developer toolsUse the shortcut for your system, then choose the Network tab.
2
Clear the listClick the clear button so only new requests show while you work.
3
Convert a fileDrop any file into a FileFormer tool and run it as usual.
4
Look for an uploadYou’ll see the page load its code, but no request carrying your file. That’s the proof.
~/pull-the-plug

The simplest proof: switch off your internet and convert.

Everything a conversion needs is already in this tab. Once the page has loaded, turn off Wi-Fi or unplug the cable, then run the conversion. The light below follows your connection live, and the result records whether you were offline when it finished.

Online: switch off Wi-Fi to test
wifi_offConvert the sample now
not run yetgo offline first, then press the button