RTS (Radio Télévision Suisse) publishes an enormous volume of French-language journalism, documentary film, cultural programming, and sports coverage. Like most mainstream broadcasters, RTS delivers that content through segmented streaming protocols — primarily DASH and HLS — which slice a single programme into hundreds of short transport chunks delivered over HTTPS. The player stitches those chunks together in real time, which is excellent for adaptive bitrate playback and terrible for anyone who wants a stable, offline copy of a segment for study, reference, or personal commentary.
Two further technical obstacles shape any archival workflow. First, manifest throttling: many broadcasters rate-limit requests per fragment or per session, so a naive single-connection download crawls or stalls entirely. Second, stream separation: high-resolution tiers (1080p, 1440p, 2160p/4K, and 60fps sports feeds) are usually served as video-only and audio-only tracks that must be muxed after download, alongside separate subtitle and audio-description tracks. A tool that cannot parallelise fragments and cannot remux will hand you an unplayable video-only file, or a soft, low-bitrate fallback.
On the legal side, this guide is grounded firmly in Fair Use, personal commentary, criticism, teaching, and educational preservation doctrine. Downloading a publicly available broadcast for private study, offline language practice, citation in research, or safeguarding a segment that may be removed from a rotating catch-up window is a defensible personal use in many jurisdictions. It is not a licence to redistribute, re-upload, monetise, or systematically mirror a broadcaster's catalogue. Respect RTS's terms of service, respect local copyright law, and treat every downloaded file as private study material rather than a distribution master.
This guide compares three practical approaches for 2026: the yt-dlp app desktop GUI, the upstream yt-dlp command-line interface, and browser-based online converters. Each is evaluated on fragment acceleration, format and resolution ceiling, subtitle track handling, playlist behaviour, and privacy posture — so you can pick the method that matches your technical comfort and your archival ambitions.
yt-dlp app (Recommended Desktop GUI)
The yt-dlp app is a proprietary desktop GUI that wraps upstream open-source utilities — yt-dlp, FFmpeg, and aria2c — inside a native Tauri v2 shell written in Rust. Because the interface layer is native rather than a browser engine, the application is fast, light on memory, and behaves like an ordinary desktop program. It targets the exact pain points of segmented broadcast streaming: it reads DASH and HLS manifests, negotiates the highest available tier including 4K and 60fps variants, and reconstructs the fragmented transport stream into a single container.
Its multi-connection fragment engine routes chunk retrieval through aria2c, opening parallel connections so a throttled manifest no longer dictates your download speed. When the video and audio tracks arrive separately, FFmpeg muxes them automatically into one playable file, and subtitle or audio-description tracks can be embedded or saved alongside. All configuration and history live in plain JSON files on your local filesystem — no account, no cloud sync, and no telemetry leaving your machine.
Step-by-Step Instructions
Step 1: Download and launch yt-dlp app
Install the desktop build for your operating system from the official distribution page and launch it to reach the main download view.
Step 2: Paste the RTS video or playlist URL
Copy the RTS page link or a playlist/series URL and paste it into the URL field, then let the app query available formats.
Step 3: Choose quality, tracks, and container
Select your target resolution — 1080p, 1440p, or 4K where offered — and choose whether to embed subtitles and audio-description tracks.
Step 4: Enable fragment acceleration and start the job
Confirm multi-connection downloading is active so aria2c parallelises fragments, then start the download and monitor progress in the queue.
Step 5: Verify the muxed output file
Once FFmpeg finishes muxing, open the resulting file to confirm audio, video, and subtitle tracks are all present and in sync.
Advantages
- ✓ Multi-connection aria2c fragment engine defeats per-fragment throttling on long RTS programmes
- ✓ Automatic FFmpeg muxing plus subtitle and audio-track selection for clean 4K/60fps archives
- ✓ Local JSON storage with zero telemetry and no account requirement
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 other tools ultimately depend on. It is a scripting powerhouse: a single command can select a format by resolution ceiling, download an entire RTS series, write metadata sidecar files, and hand post-processing to FFmpeg. For batch archival, scheduled capture, or integration into an existing media pipeline, nothing matches its precision or its breadth of extractor support.
The trade-off is ergonomics. There is no queue view, no thumbnail grid, and no visual confirmation of what you are about to fetch. You must know your flags — format selection strings, output templates, subtitle options, and concurrency settings — and you must install and maintain yt-dlp, FFmpeg, and aria2c yourself, keeping each one updated so extractors continue to work as RTS changes its delivery stack.
Step-by-Step Instructions
Step 1: Install the toolchain
Install yt-dlp, FFmpeg, and aria2c through your system package manager or the official release binaries, and confirm each responds on the command line.
Step 2: Inspect available formats
Run a format-listing command against the RTS URL to see which video-only, audio-only, and subtitle streams the manifest exposes.
Step 3: Build your download command
Compose a format selector for your target resolution, add an output template, and enable external downloader arguments for parallel fragments.
Step 4: Execute and post-process
Run the command and let FFmpeg merge the separate video and audio tracks, embedding subtitles if you requested them.
Step 5: Script it for repeat captures
Move the working command into a shell script or scheduler so recurring RTS programmes are archived automatically.
Advantages
- ✓ Open-source upstream engine with the most granular format and metadata control
- ✓ Ideal for automation, cron-scheduled captures, and repeatable scripted workflows
- ✓ Same core technology used by the GUI, so output quality is equivalent
Drawbacks
- ✗ Steep learning curve — flag syntax and format strings must be memorised
- ✗ Manual dependency management for yt-dlp, FFmpeg, and aria2c, including updates
Web-Based Online Converters
Browser-based converter sites are the lowest-friction option: paste a link, click a button, wait, and receive a file. They require no installation and work from any device, including phones and borrowed computers. That convenience is genuinely useful for a one-off clip where nothing else is available.
The costs are significant and often invisible. These services usually cap output resolution well below what RTS actually serves, and many silently re-encode the result, discarding bitrate, HDR metadata, and 60fps motion smoothness. Because the download happens on someone else's server, your request is logged and your URL is shared with a third party, while the surrounding pages are typically saturated with redirect ads, fake download buttons, and tracking scripts. Server-side rate limits also mean long programmes frequently fail partway through.
Step-by-Step Instructions
Step 1: Locate the RTS page URL
Copy the full address of the RTS programme page you want to convert.
Step 2: Paste into a converter site
Enter the link into the converter's input field and submit it, closing any pop-up windows that appear.
Step 3: Pick the offered quality
Choose from whatever resolutions the service exposes, accepting that the highest tier is usually unavailable.
Step 4: Download and check the file
Retrieve the generated file and verify its resolution, audio sync, and duration before relying on it.
Advantages
- ✓ No installation — works immediately in any modern browser on desktop or mobile
- ✓ Simple single-file flow for short, casual clips
Drawbacks
- ✗ Intrusive ads, redirect pop-ups, and aggressive third-party tracking
- ✗ Privacy risk — the target URL and your IP are logged server-side
- ✗ Strict resolution caps and lossy re-encoding, with no subtitle track support