Bloomberg publishes some of the most time-sensitive business journalism on the internet: earnings calls, market-open segments, executive interviews, and long-form documentary reporting. When you need to archive that material for research, citation, or teaching, you are not fighting a simple video file — you are fighting a delivery pipeline. Bloomberg's player streams through segmented protocols such as DASH and HLS, meaning a single 12-minute clip may arrive as hundreds of small encrypted chunks requested sequentially by a JavaScript player. Add adaptive bitrate switching, per-session tokens, regional rate limiting, and aggressive throttling on burst requests, and the naive "right-click and save" approach collapses immediately.
The second challenge is fidelity. Bloomberg streams carry multiple video renditions up to 4K where available, 60fps variants for smooth ticker and studio motion, separate audio tracks, and distinct subtitle or caption tracks. A downloader that grabs only the default rendition gives you a soft 720p file with burned-in captions and no way to recover the original. Proper archival means selecting the video track, selecting the audio track, and muxing them locally into a single container without re-encoding — a job that requires a real fragment engine and a real muxer on your own machine.
On legality: downloading a publicly accessible stream for personal study, commentary, criticism, teaching, or news reporting generally falls within fair use and similar exceptions in many jurisdictions, but this is not legal advice. What matters is that you do not redistribute the file, do not evade paywalls, and do not commercialize the archive. The practical corollary is that your archiving workflow should be as private as your viewing habits — which is precisely why this guide contrasts local desktop execution against cloud converters that log your IP address, the exact URL you submitted, and a timestamp that links the two.
Below are three methods, ranked by reliability, output quality, and respect for your privacy. Method one is the yt-dlp app, a proprietary desktop GUI built on top of upstream open-source utilities. Method two is the raw yt-dlp command-line interface. Method three is web-based online converters, which we examine critically rather than recommend.
yt-dlp app (Recommended Desktop GUI)
The yt-dlp app is a proprietary desktop application built with Tauri v2 and Rust, wrapping upstream open-source utilities — yt-dlp, FFmpeg, and aria2c — behind a clean graphical interface. It is not open source and not free-forever, but its engineering is transparent where it counts: the fragment engine drives multiple concurrent connections per stream, which is exactly what you need to defeat Bloomberg's per-connection throttling on segmented DASH manifests.
When a download completes, FFmpeg automatically muxes the selected video and audio renditions into a single container without quality loss, and subtitle tracks are written alongside as separate files. State is kept in local filesystem JSON storage with zero telemetry — nothing about your queue, your URLs, or your IP address ever leaves the machine.
Step-by-Step Instructions
Step 1: Download and launch yt-dlp app
Install the desktop build for your operating system and open it. No account, sign-in, or browser extension is required.
Step 2: Paste the Bloomberg video or playlist URL
Copy the watch page link or a playlist/collection URL and paste it into the source field. The app enumerates every entry in a playlist automatically.
Step 3: Select quality, framerate, and tracks
Choose your target rendition — up to 4K and 60fps where Bloomberg offers it — then tick the audio and subtitle tracks you want included in the output.
Step 4: Enable multi-connection acceleration
Confirm the aria2c multi-connection engine is active so large fragments download in parallel rather than one at a time.
Step 5: Download and mux to a local file
Start the job; FFmpeg muxes the selected tracks into a single container and writes it to your chosen folder, with subtitles saved alongside.
Advantages
- ✓ Multi-connection aria2c fragment engine accelerates segmented DASH/HLS streams and defeats per-connection throttling
- ✓ Automatic FFmpeg muxing preserves 4K, 60fps, and separate audio/subtitle renditions without re-encoding
- ✓ Zero telemetry with local filesystem JSON storage — queue, history, and URLs never leave your desktop
Drawbacks
- ✗ Requires desktop installation
Ready to download yt-dlp app? 🚀
Experience native speed, 4K/8K stream extraction, and zero telemetry video archiving on Windows, macOS, and Linux. ✨
Get yt-dlp appyt-dlp (Command Line Interface)
The upstream yt-dlp CLI is the open-source engine that most graphical tools, including the desktop app above, are ultimately built upon. It is genuinely free and community-maintained, and it is unmatched for automation: a single command with a format selector can resolve the best video and audio streams, merge them, embed subtitles, and name the output by upload date.
The trade-off is terminal fluency. You must understand format strings, output templates, cookie files, and rate-limit flags, and you must install and keep FFmpeg and aria2c on your PATH yourself. For a one-off or for a scheduled batch job run from a script, that power is worth the friction; for casual archival it is a steep climb.
Step-by-Step Instructions
Step 1: Install yt-dlp and dependencies
Install the CLI plus FFmpeg for muxing and aria2c if you want multi-connection downloading, then verify each is reachable on your PATH.
Step 2: Inspect available formats
Run a list-formats command against the Bloomberg URL to see the actual resolution, framerate, codec, and audio track IDs on offer.
Step 3: Build your format selector
Compose a selector that pairs the best video stream with the best audio stream, and specify a subtitle language flag if captions exist.
Step 4: Add acceleration and naming flags
Pass the external-downloader flag for aria2c plus a concurrent-fragment count, and set an output template that records the title and date.
Step 5: Execute and archive
Run the command, let FFmpeg merge the streams, and verify the resulting container plays back with audio and subtitles intact.
Advantages
- ✓ Open-source upstream utility with the broadest extractor coverage and fastest patch cadence
- ✓ Fully scriptable — cron jobs, batch URL lists, and format-string automation without any GUI
- ✓ Granular control over format selection, cookie handling, and output naming templates
Drawbacks
- ✗ Steep learning curve requiring comfort with terminal commands and format syntax
- ✗ Manual dependency management — you install and update FFmpeg and aria2c yourself
Web-Based Online Converters
Browser-based downloader sites are the most visible option and the least defensible. You paste a Bloomberg URL into a form, wait behind a queue, and receive a file — usually a single pre-muxed rendition, often transcoded down to 360p or 720p because the service caps resolution to conserve bandwidth.
The real cost is not the quality, it is the exposure. The URL you submit is frequently a signed, session-linked address, and the operator of that website now has it, along with your IP address, your user agent, and a timestamp. Many of these sites are funded by redirect chains, fake download buttons, and interstitial pop-ups, and some inject watermarks or strip subtitle tracks entirely.
Step-by-Step Instructions
Step 1: Paste the URL into the converter
Submit the Bloomberg link to the web form, understanding that the URL and your IP are now recorded by a third party.
Step 2: Dismiss the interstitial layer
Close the pop-ups and redirect overlays that typically appear before a real download control is reachable.
Step 3: Select from the limited presets
Pick from whatever low-resolution presets the service exposes, since 4K and 60fps options are rarely offered.
Step 4: Retrieve the compressed output
Download the single muxed file and check it for watermarks, missing audio, and absent subtitle tracks.
Advantages
- ✓ No installation — works from any browser on any device
- ✓ Simple single-field interface with no technical configuration required
Drawbacks
- ✗ Intrusive ads, redirect chains, and deceptive download buttons that can lead to malware
- ✗ Privacy tracking — submitted URLs, IP addresses, and timestamps are logged server-side
- ✗ Strict resolution caps, server-side throttling, and lossy re-encoding that degrades or strips 4K, 60fps, and subtitle tracks