Initializing... drag & drop files here
Supports: SWF
This walks you through rendering a Flash (.swf) animation into an M2TS file — the BDAV MPEG-2 Transport Stream that Blu-ray discs and AVCHD camcorders use — so a stranded Flash-era clip can feed a Blu-ray-authoring or high-definition editing pipeline that only ingests transport-stream video. It is for people rescuing old animations into a disc-authoring workflow, and it is honest about the two things that trip this conversion up: SWFs that draw themselves with code rather than a timeline, and the fact that a single .m2ts stream is not the same thing as a finished, burnable Blu-ray.
.swf onto the page or click "Add Files" — pull in animations exported from Macromedia/Adobe Flash, saved from old Newgrounds or Albino Blacksheep archives, or grabbed from the Wayback Machine. Batch is supported; drop a folder and each file renders in parallel..m2ts on our servers — no Flash Player install, no sign-up, no watermark.On this page the output defaults to H.264 video with AAC audio, which plays in software players and imports cleanly into most authoring tools. The native AVCHD spec actually pairs H.264 with AC-3 (Dolby Digital) or LPCM audio — not AAC — so if your downstream authoring template is strict about the AVCHD audio spec, switch the Audio Codec to AC3 under Advanced Options before converting. The video codec is best left on H.264 for Blu-ray and AVCHD work; the other selectable codecs serve narrower needs:
loadSound() to pull audio from a server that is now gone, there is nothing to decode and the output is silent.M2TS is a niche target, so reach for it only when something downstream genuinely requires a transport stream. The conversion can also fall short in a few ways: a heavily interactive SWF (clickable menus, mini-games, branching ActionScript) only captures whatever plays without input, not the interactive experience; an encrypted or DRM-protected SWF cannot be parsed; and the .m2ts you download is a single stream, not an authored disc — burning it raw will not produce a Blu-ray a set-top player can navigate. For a modern, smaller, far more widely supported result, SWF to MP4 carries the same H.264 in a file phones, browsers, and ordinary editors all accept; if you are cutting on a timeline, SWF to AVI suits editing-era workflows; and to keep an interactive SWF clickable, preserve it in Ruffle rather than flattening it to video.
Not on its own. What you download is a single video stream — the kind that lives inside a Blu-ray's BDMV/STREAM/ folder — not a finished, authored disc. A real Blu-ray or AVCHD structure also needs the playlist and clip-information files that a loose stream does not include, so burning this file raw will not create a disc a set-top player navigates. The .m2ts plays in software players such as VLC and feeds authoring tools (tsMuxeR, multiAVCHD) that build the disc structure around it.
They are the same BDAV MPEG-2 Transport Stream. .m2ts is the long-filename style used on Blu-ray discs and PCs, while .mts is the 8.3 name AVCHD camcorders write to the memory card; the bytes inside are the same multiplexed H.264 stream. If your workflow specifically wants the camcorder-style name, use SWF to MTS instead — otherwise .m2ts is the more common choice for disc-authoring tools.
Two SWF types cause this. Script-driven SWFs that draw the scene with ActionScript or load assets at runtime render empty, because the converter parses the file rather than executing Flash code. And interactive SWFs — games, branching menus — only yield whatever plays without user input. Plain timeline animations convert reliably. If a code-driven or interactive SWF matters, keep it playable in the open-source Ruffle emulator instead of flattening it to a video stream.
Yes, if the audio is embedded in the SWF. A Flash timeline's streamed MP3 or its ADPCM sound effects are decoded and re-encoded — into AAC by default, or AC-3 if you select it for an AVCHD-spec workflow. Audio the SWF pulled from an external server with loadSound() will not carry over if that server is gone, because there is nothing left to decode; only audio baked into the file survives.
Choose M2TS only when a Blu-ray or AVCHD pipeline specifically demands a transport stream. For almost anything else — phones, browsers, smart TVs, ordinary video editors — SWF to MP4 wraps the same H.264 video in a smaller, far more widely supported container. M2TS earns its place when an authoring tool refuses to ingest MP4 and wants the BDAV stream directly.
Your SWF is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion. There is no sign-up, no watermark, and your files are never shared or made public.