Initializing... drag & drop files here
Supports: SWF
.swf files, or click "+ Add Files" to browse. Batch conversion is supported — every file uses the same settings.Adobe Flash Player reached end of life on December 31, 2020, and Adobe blocked Flash content from running in the player starting January 12, 2021. Every major browser — Chrome, Edge, Firefox, Safari — removed the Flash plugin in the same window. That means SWF files (the playback format Macromedia/Adobe Flash exported since 1996) no longer play in any modern browser without a third-party emulator like Ruffle. Re-encoding to WebM puts the visible video back inside an HTML5 <video> element that every current browser handles natively.
<video> tag and it plays in Chrome, Firefox, Edge, and Safari 14.1+ (macOS) / iOS 14.5+ without any plugin.| Property | SWF (Flash) | WebM |
|---|---|---|
| Container introduced | 1996 (Macromedia FutureSplash) | 2010 (Google, royalty-free) |
| Status in 2026 | End-of-life since Dec 31, 2020 | Actively maintained by WebM Project |
| Native browser support | None — Flash plugin removed from all browsers | Chrome, Edge, Firefox, Opera, Safari 14.1+ |
| Video codec | Sorenson Spark / H.263 / VP6 / H.264 (later versions) | VP8, VP9, or AV1 |
| Audio codec | MP3, ADPCM, Nellymoser, Speex, AAC | Vorbis or Opus |
| Vector + ActionScript | Yes — interactive scripting and timelines | No — pure video/audio |
| Transparency (alpha) | Yes (vector) | Yes (VP9 with alpha) |
| Streaming-friendly | Limited — designed for plugin playback | Yes — segmented delivery, MSE support |
| Typical use today | Legacy archives only | Web video, HTML5 <video> element |
| Setting | VP9 (default) | VP8 |
|---|---|---|
| Year shipped | 2013 (Chrome 29) | 2010 (Chrome 6) |
| Browser support | Chrome, Edge, Firefox, Opera, Safari 14.1+ (macOS), iOS 14.5+ | Same set, plus older Safari builds |
| Bitrate efficiency | ~40-50% smaller than VP8 at equal quality | Larger files |
| Encode speed | Slower | Faster |
| Audio pairing | Opus (recommended) | Vorbis or Opus |
| Use when | Modern web delivery, archiving, alpha needed | Maximum compatibility with very old WebM decoders |
Because the Adobe Flash Player plugin was discontinued on December 31, 2020 and removed from Chrome, Edge, Firefox, and Safari. Adobe also blocked any remaining installed players from running Flash content starting January 12, 2021. SWF is now a "dead" runtime format — the only way to view the contents on modern devices is to extract the video/animation track to a format like WebM or MP4, or to use a Flash emulator such as Ruffle (which only supports a subset of ActionScript).
It re-renders the visible content. SWF is a vector + ActionScript runtime, not a video container, so a frame-accurate capture is the only reliable approach. Animations built from vector shapes, tweens, and bitmap libraries all flatten into rasterized frames at the resolution you choose. If the SWF was simply a wrapper around an embedded FLV/H.264 stream, the output will match the source bitrate quality closely; if it's a heavily-scripted interactive piece, only the deterministic animation path will be captured.
No — and no SWF-to-video converter can preserve them, because the output is plain video. WebM, MP4, and every other modern video container have no equivalent of ActionScript. If the SWF is a game, a quiz, or a click-driven module, you'll get a recording of the default animation path only. For interactive Flash content, evaluate Ruffle or an HTML5 re-authoring approach instead of conversion.
VP9 in almost every case. It's the default for a reason — VP9 cuts file size roughly in half at the same visual quality, ships in every browser since Safari 14.1 added it in April 2021, and supports an alpha channel for transparent overlays. Choose VP8 only if you specifically need compatibility with very old WebM decoders that predate VP9 (Chrome 6-28, very early Android builds) — extremely rare in 2026.
Yes — re-encoding a small source to a larger resolution always upscales the pixels; the converter can't invent detail that wasn't in the original. Keep the output at the SWF's native stage size (or use a multiple of it like 2× or 3× for cleaner integer scaling) unless you specifically need a larger frame. For vector-heavy Flash, render at 2× the original stage size for a crisper result while still keeping the file small.
It matches the SWF's stage frame rate, which is most commonly 12, 24, or 30 fps for Flash content. If you're embedding the WebM into a 60 fps website player, that's fine — the browser simply repeats frames. There's no advantage to forcing the output to a higher fps than the source animation.
Yes. SWF audio (MP3, ADPCM, or Nellymoser in older files; AAC in later F4V-style exports) is re-encoded to Opus inside the WebM container by default, which is the recommended pairing for VP9. If you need a different audio codec (Vorbis for legacy compatibility), open Advanced Options → Audio Codec.
Smaller than the source SWF in most cases. SWFs that bundle high-resolution bitmaps and uncompressed audio can be surprisingly heavy; VP9 + Opus is far more efficient. A typical 5-minute SWF cartoon at 720p comes out around 15-40 MB. If you need a specific target, set Advanced Options → File Compression → "Specific file size" and the encoder will adjust bitrate to hit it.
Yes. Use Convert SWF to MP4 for H.264/MP4 output (better for hardware playback on older TVs and phones), Convert SWF to MOV for editing in Final Cut or Premiere, or Convert SWF to GIF for silent looping animations under ~5 seconds.