How your data flows
- Files are opened through the browser file picker.
- JavaScript, WebAssembly, Canvas, WebCodecs and browser codecs process content in the current tab.
- Results are exposed as temporary object URLs in the browser.
- Removing a file or closing the tab discards those temporary references.
LocalFileLab has no file upload endpoint for the converter. Ads and external runtime components do not automatically receive access to selected files.
Browser sandbox and memory
Processing stays inside the browser security boundary. LocalFileLab can only read files you explicitly select or drop. Results remain in memory or temporary browser resources until downloaded or removed.
Very large or malformed files can consume substantial memory and processing time. Use an up-to-date browser and keep enough memory available.
External runtime resources
Some media operations load FFmpeg/WebAssembly components from jsDelivr. OCR may download worker and language data used by Tesseract. These requests expose normal connection data, but not the contents of your selected files.
Google AdSense is embedded as a separate advertising system. It has no programmatic access to selected file contents, but may process its own technical data. See Privacy for details.
Metadata and output files
Depending on the format, you can preserve or remove compatible metadata. Metadata may contain names, timestamps, device details, location data or embedded artwork. Review sensitive outputs before sharing.
Use LocalFileLab safely
- Process confidential files only on a trusted and updated device.
- Download the output and then remove it from the list.
- Continue to treat unknown archives and documents cautiously.
- On shared devices, use a private browser profile and close the tab afterwards.
Report a vulnerability
Do not include sensitive file contents in a public issue. Security concerns can be reported through the repository security area.