Workspace · DownloaderExplicit URLThis lane can be linked directly from guides, hubs, and future batch flows. Stable runtimeThe underlying downloader stays on the current bundle, so risk stays low. Growth pathFuture subtitle/video lanes can follow the same split pattern.
Run export work inside a dedicated downloader lane.
This page uses the stable runtime bundle, but the route is now explicit and shareable.
Bundle-backed lane
The runtime stays stable while the route becomes explicit.
Keep the current downloader logic, but stop forcing every bookmark through one generic tab URL.
Capability boundary
Browser download is conditional. Inspect the manifest before you commit to a queue or export path.
- Encryption, token expiry, and missing segments can stop a browser-side download.
- Preserve manifest analysis and variants even when the download step degrades.
- Queue repeat work instead of blocking the first screen with long runs.
Mobile execution
On narrow screens, keep the current task visible first and collapse helper rails into secondary controls.
- Player and inspector remain primary mobile modes.
- Queue, history, and settings should stay reachable without dominating the first screen.
- Avoid introducing extra fixed panels that cover inputs or results.
Storage contract
Saved playlists stay in Local Storage. TXT is the everyday import/export format and JSON remains the backup format.
- Playlist keys: m3u8-playlists, m3u8-recent-playlists.
- Settings key: m3u8-last-used-settings.
- Import TXT for routine work; use JSON only for backup and restore.
Execution surface
Downloader runtime
The current M3U8 downloader bundle is mounted below.
M3U8 Toolkit
Loading workspace lane…
Low-interference sponsor slotView ad policy
Sponsor cards stay after the execution surface instead of cutting across the main input or primary action.
Slot IDad-ws-sponsor-primary-m3u8-downloader
Placementsponsor-card
Modeself-promo
Densitylight