Initializing... drag & drop files here
Supports: SWF
M2TS is the MPEG transport stream flavour used on Blu-ray discs and AVCHD camcorders, and it is what set-top boxes, media players and hardware editors tend to accept without argument. This converter reads the video and audio streams embedded in a .swf, re-encodes them, and muxes the result into a .m2ts file. Adobe stopped supporting Flash Player on December 31, 2020 and began blocking Flash content on January 12, 2021, so moving Flash video into a transport stream is a way to get it into equipment that will still play it years from now.
Worth settling before you upload: nothing here emulates the Flash runtime. We decode what is stored in the container, not what ActionScript would have drawn.
.swf onto the page or click "+ Add Files". Several files can be queued and converted with one set of settings..m2ts. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.The output really is BDAV-framed: our encoder writes 192-byte packets — a standard 188-byte transport packet with a 4-byte arrival-timestamp prefix in front of it — rather than the plain 188-byte packets you get from a .ts or .mts file. Checking the first bytes of our own output confirms the sync byte 0x47 sitting at offset 4 rather than offset 0, which is exactly the BDAV layout.
That framing is only half of what a Blu-ray player expects, though. AAC is not a legal audio codec for BDAV, and it is what this page selects by default. Blu-ray audio means AC-3, DTS or linear PCM. If the file is destined for a disc-authoring tool or a player that follows the spec strictly, change Audio Codec to AC3 before converting. If it is going into VLC, a PC media player or an NLE, AAC is fine and more efficient.
| Property | What you get here | What a Blu-ray disc requires |
|---|---|---|
| Packet framing | 192-byte BDAV packets | 192-byte BDAV packets |
| Video codec | H.264 by default | H.264, MPEG-2 or VC-1 |
| Audio codec | AAC by default | AC-3, DTS or LPCM — change this |
| Directory structure | A single loose .m2ts file |
A full BDMV/STREAM/ layout |
Even with AC-3 selected, a single .m2ts is a stream file, not a disc. Authoring software will take it as an input and build the BDMV structure around it; simply renaming or copying the file onto a disc will not produce something a player can navigate.
| Property | In the .swf |
In the .m2ts |
|---|---|---|
| Video | Sorenson Spark, VP6 or Flash Screen Video | Re-encoded to your chosen codec |
| Audio | MP3, ADPCM or Nellymoser stream | Re-encoded to your chosen codec |
| Duration | Not declared in the header at all | Written properly once encoded |
| Interactivity | Buttons, ActionScript, input handling | Lost — a transport stream is linear video |
| Vector artwork | Shapes redrawn by the Flash Player | Not present unless it was encoded as video |
Every conversion re-encodes; the streams are decoded and compressed again rather than copied across. That costs a generation of quality, so pick the highest Quality Preset you can live with if the result will be edited further.
Because it very likely holds no encoded video stream. Most .swf files that survive today are vector timelines — games, banners, menus, cartoons — where the artwork was described as shapes and drawn by the Flash Player at runtime rather than stored as pixels. A converter that reads embedded streams finds nothing to read. Encrypted and anti-decompiler-protected files fail too. A Flash emulator such as the open-source Ruffle is the only route for that kind of file, and you would be capturing its playback rather than converting.
MP4, unless something specific requires a transport stream. MP4 is smaller for the same quality, plays on every phone, browser and editor, and is far easier to move around. M2TS earns its place when the destination is Blu-ray authoring, an AVCHD workflow, a broadcast chain, or a set-top box that will not read MP4. For general viewing and sharing, SWF to MP4 is the better answer.
Yes, provided the SWF actually contains an audio stream — it is decoded and re-encoded to your chosen Audio Codec alongside the video. If the Flash file's sound was generated at runtime by ActionScript rather than stored, there is nothing to carry over and the output will have video only. Note that Flash movies frequently contain far less audio than their runtime suggested.
Not from the .swf itself. Flash files are not seekable — there is no index for a decoder to jump into — so asking for a start offset inside a SWF will not land where you expect. Convert the whole movie first, then cut the result, which is a format that seeks properly. Converting whole is also the only way to find the real length, since a SWF header declares a frame count and frame rate instead of a duration.
Stay on Quality Preset unless you have a reason not to; it is the default and it behaves sensibly across all the codecs offered here. Switch to Constant Quality if you want to drive the CRF slider directly — on H.264 and H.265 it runs 16-51, where lower means better quality and a larger file, and the low twenties is the usual sweet spot. Reach for Specific file size or a bitrate mode only when you have a hard number to hit, such as a disc capacity.
It will look exactly as good as the Flash video did, which is usually modest. Flash video was authored for small players on dial-up-era connections — frequently 320x240 or 480x360, at low bitrates. Upscaling to 1080p during conversion enlarges the pixels without adding detail and makes the compression artefacts more obvious. Leaving Video resolution on "Keep original" and letting the TV do the scaling generally looks better.
All three carry MPEG transport streams, but the framing differs. A .m2ts file uses 192-byte BDAV packets with a 4-byte timestamp prefix on each one, which is what Blu-ray and AVCHD expect. .ts and .mts files use plain 188-byte packets. Our encoder follows the extension you choose, so requesting .m2ts genuinely produces the BDAV layout rather than a renamed .ts.
None of it. Buttons, links, mouse handling, game logic and anything else driven by ActionScript are properties of the Flash runtime, not of the video. A transport stream is a linear sequence of pictures and sound. If the interactive behaviour is the thing you need to preserve, no video conversion will do it — you need an emulator that runs the original file.
Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — never shared, never made public, and never used for anything other than producing your download.