Files can carry more information than the content you immediately see. This guide explains the practical details so you can choose what to keep, remove or verify before sharing.
The browser can read local files you select
Modern web APIs let a page access a file only after you choose or drop it. JavaScript can read the bytes in memory, decode supported images, and create a new output without sending those bytes to an application backend.
Canvas can rebuild images
For image cleaning, the browser decodes the source into pixels, draws those pixels to a canvas, and encodes a new image. Metadata that is not part of the rendered pixels is typically not carried into the fresh output.
Downloads can be generated locally
The page can create a Blob and temporary object URL for the result. Clicking Download saves that generated file directly from browser memory.
Local does not mean zero network traffic
The website itself still needs to load HTML, CSS, scripts, fonts, ads or analytics unless they are fully self-hosted. A transparent privacy policy should distinguish file processing from ordinary website requests.
Use the relevant BeOutMeta tool on a copy of your file, then review the result before publishing or sending it.
Browse tools