How to Verify Local Execution Using Your Browser's Network Tab

"Your file never leaves your device" is easy to say. The good news: you don't have to trust it — your browser ships with a tool that lets you check. This guide shows how to watch the network yourself while a tool runs, so you can confirm nothing is uploaded.

Open the developer tools

On the page you want to test, press F12 (or right-click → Inspect). This opens your browser's developer tools. Works the same in Chrome, Edge, Firefox and Safari (enable the Develop menu first on Safari).

Switch to the Network tab

Click the Network tab. This records every request the page makes — every file it fetches and, crucially, anything it tries to send.

Clear the log and start recording

Click the clear (🚫) button so you start from a clean slate. Make sure recording is on (the record dot is red/filled). Optionally tick Preserve log so entries survive any page updates.

Run the tool with a test file

Now use the tool as normal — for example, drop a photo into the Metadata & EXIF Privacy Scrubber and process it. Watch the Network tab as you do.

Read what you see

For a genuinely local tool, you'll see requests only for the page's own code and assets (scripts, styles, fonts) — no request that uploads your file. Look specifically for POST or PUT requests carrying a large payload the size of your file; there shouldn't be any. You can click any request and check its "Payload" / "Request" body to be sure your file's bytes aren't in it.

Make it a habit

This check takes under a minute and works on any web tool, not just Orilami's. Before trusting a site with something sensitive, watch its network while it works. If your file gets uploaded, you'll see it. If it doesn't, you've verified the privacy claim for yourself.

A promise you can verify beats a promise you can't. Orilami's tools are built so this check always comes back clean.