WTV to SWF Converter

How to Convert WTV to SWF Online

1. Upload Your WTV File: Drag and drop the .wtv recording, or click "+ Add Files" to browse. Batch conversion is supported, useful when you're flattening a folder of old Windows Media Center captures in one pass.
2. Pick a Video Codec and Quality Preset: Default codec is FLV (Sorenson Spark, H.263), the SWF-native option that plays in Ruffle and legacy Flash Players. Switch to H.264 if your target SWF player wraps the AVC bitstream (Flash Player 9.0.115.0+ from December 2007 onward). Set Quality Preset to Very High (default), High, Medium, Low, or Lowest, or pick Constant Bitrate / Constant Quality / Constraint Quality under File Compression and target a specific kbps or Mbps.
3. Resize and Trim (Optional): Use Preset Resolutions (240p through 4320p), Resolution Percentage, Width x Height, or single-side Width / Height with aspect lock. SWF was designed for embedding at fixed stage sizes — 640x480 or 854x480 is a safe choice for desktop, 320x240 if you're matching a 2000s-era Flash project. Trim with Time Range to drop pre-roll, commercials, or the trailing pad WMC tacks on.
4. Convert and Download: Click Convert. The file processes on our servers and is ready in seconds to a few minutes depending on length. No sign-up, no watermark, no email gate.

Why Convert WTV to SWF?

WTV is Microsoft's proprietary container for Windows Media Center recordings, introduced with the Vista Media Center TV Pack 2008 and shipped through every Windows 7 Media Center edition. It carries MPEG-2 or H.264 video alongside AC-3 or MPEG-1 Layer II audio, plus a metadata layer with episode titles, channel logos, and air dates. Microsoft discontinued Media Center entirely in Windows 10 (announced May 2015), and Windows 10/11 upgrades silently remove it. That leaves WTV recordings stranded — no native player on modern Windows, no Mac or mobile support, and a DRM "broadcast flag" that can lock encrypted captures even on the original PC.

SWF (Small Web Format, originally ShockWave Flash) is the opposite kind of legacy: an authoring-era container designed by FutureWave in 1996, owned by Macromedia then Adobe, and end-of-lifed by Adobe on December 31, 2020. Adobe Flash Player blocked all SWF playback on January 12, 2021. So why convert WTV to SWF in 2026? Niche archival reasons, and they're real:

• Embedding into a preserved Flash project — if you're restoring a 2005-2012 Flash CD-ROM, museum kiosk, or Newgrounds-era multimedia piece that loads external SWF clips via loadMovie(), you need the source video as an SWF, not MP4.
• Ruffle-based replay — Ruffle, the open-source Flash emulator written in Rust, runs many ActionScript 1/2 SWFs in modern browsers, letting you republish a Flash-era exhibit without Adobe's runtime.
• Vector-rich slideshow output — SWF was strong at compositing low-frame-rate footage over vector overlays, useful when an archived training module needs a TV clip dropped back into its original .fla.
• Sub-minute teasers for legacy CMSes — some long-running intranet sites, library kiosks, and educational repositories still serve .swf content because the surrounding portal hasn't migrated.
• Format-research and digital-preservation work — institutions documenting the Flash era convert canonical sources into SWF to test players, emulators, and crawlers against representative payloads.

For everyday playback (phone, smart TV, YouTube upload, modern browser), convert WTV to MP4 instead — see WTV to MP4. SWF is a deliberate, archival choice.

WTV vs SWF — Format Comparison

SWF Codec Quick Guide

Frequently Asked Questions

Why would anyone still convert anything to SWF in 2026?

Three honest reasons: restoring a preserved Flash project that loads external .swf clips, republishing through the Ruffle emulator (open-source, MIT/Apache 2.0, runs in Chrome/Firefox/Edge), or feeding a legacy CMS that hasn't been migrated. For ordinary playback on a phone, TV, or modern browser, SWF is the wrong answer — use MP4. We support the conversion because digital-preservation and Flash-archival workflows still need it.

Will the SWF play in a modern browser like Chrome or Firefox?

Not natively. Chrome, Edge, Firefox, and Safari all removed Flash Player support by January 2021. The realistic playback path today is Ruffle, an open-source Flash emulator written in Rust. Ruffle handles most ActionScript 1 and ActionScript 2 content well; ActionScript 3 support is still being completed, so a complex AS3 SWF may not render perfectly.

My WTV recording is "Protected" — will it convert?

If the broadcast flag and Microsoft's PlayReady DRM are set, the file is bound to the original PC's machine certificate and FFmpeg-based decoders (which our pipeline uses) cannot read the protected stream. You'd need to play it back through the original Media Center install and capture it, or look for a legacy unprotection utility. Unprotected WTV recordings — most ATSC over-the-air captures and any clip you marked as exportable — convert without issue.

Should I pick FLV/Sorenson, VP6, or H.264 for the SWF codec?

FLV (Sorenson Spark, H.263) is the safest default — every Flash Player from version 6 onward decodes it, and Ruffle supports it. Pick H.264 only if your target player is Flash Player 9.0.115.0 or later (released December 3, 2007) and you specifically need the better quality-per-bitrate ratio. VP6 sits in between and is mostly useful when matching an existing Flash 8-era authoring file.

How does the WTV audio (AC-3) get into the SWF?

SWF doesn't carry AC-3 (Dolby Digital), so the audio is transcoded on the fly. Default output is MP3, which every Flash Player supports. ADPCM and Nellymoser are also available if you're matching a specific authoring requirement — Nellymoser was historically used for microphone recordings, ADPCM for sound effects. For a TV recording, leave it on MP3.

What resolution should I export the SWF at?

SWF assumes a fixed "stage" size, so pick a resolution that matches the project you're embedding into. Common Flash-era stages are 320x240 (early CD-ROM), 640x480 (standard desktop), and 854x480 (16:9 widescreen, mid-2000s onward). Going above 1080p inflates the file with no real benefit — Flash Player and Ruffle don't accelerate high-resolution video the way HTML5 <video> does, so 480p-720p is the practical sweet spot.

Why is my SWF much smaller than the original WTV?

WTV files from over-the-air ATSC capture are typically 5-8 GB per hour because they store the raw MPEG-2 transport stream at 12-19 Mbps. SWF's Sorenson and VP6 codecs were designed for 2000s-era dial-up and DSL bandwidth, so even Very High quality at 720p lands closer to 1-2 Mbps. Expect a 5x-15x size reduction. If you want to keep the original bitrate, use Constant Bitrate and dial it up explicitly.

Is there a file-size limit on the converter?

Single-file uploads run up to several gigabytes, processed on our servers, which covers most multi-hour WTV recordings. For files at the upper end, trim with Time Range first — most archival use cases only need a clip, not the full broadcast with commercials. If you need a different output format alongside SWF, see WTV to FLV for Flash Video (similar codec stack, different container), WTV to MKV for a modern lossless archive container, or trim WTV to clip before converting.

Will the WTV metadata (episode title, channel, air date) carry over?

No. SWF is an authoring container with no equivalent of WTV's broadcast-metadata blocks, so episode title, channel logo, and original air date are dropped during conversion. If preserving that metadata matters, convert to WTV to MKV instead — MKV's tag system can hold all of it — and only convert to SWF the specific clip you need embedded.