Local file processing boundary
When you select a local file, FileReader loads its text into browser memory. Editing, analysis, comparison, conversion, and export happen in that client-side workspace, and the playlist is not intentionally posted to an M3U Studio application server. Refreshing the page clears the in-memory playlist unless you downloaded an export.
Import by URL is not purely offline: the browser requests the supplied address. The stream checker also requests each tested URL. The destination servers can observe normal connection data, so do not test or import URLs you are not authorized to use.
Block Dangerous Protocols
Our editor sanitizes incoming links and blocks unsafe injection protocols (like javascript: or file:), protecting your device from local exploits.
Security Auditing Guidelines
Separate playlist handling from the surrounding website. M3U Studio includes Google Analytics and Google AdSense code, and the hosting platform may retain access/security logs. The Privacy Policy explains those services. The application does not intentionally send locally parsed playlist contents to them for analytics or advertising.
Safely Storing Local State
The playlist workspace is held in browser memory and is discarded on refresh. Theme and language choices are saved in localStorage. To preserve playlist changes, export a new file before closing or refreshing the tab; keep the original separately so cleanup operations are reversible.