Initializing... drag & drop files here
Supports: CR2
CR2 is Canon's second-generation RAW photo — the unprocessed 14-bit sensor data your DSLR wrote before any white balance or exposure was baked in — and M2TS is the AVCHD transport-stream file as it is spelled on a computer or inside a Blu-ray disc structure. This converter renders one Canon photo and packages it as that stream, for the narrow case of dropping a still into a Blu-ray-authoring project or an AVCHD-era timeline that expects the .m2ts extension. The honest catch up front: .m2ts and .mts carry the same encoded H.264 video, but they are not the same file. The .m2ts written here is BDAV-framed — 192-byte packets that each prefix a 4-byte timestamp header ahead of the sync byte — while CR2 to MTS writes plain 188-byte transport-stream packets with no such header. Same picture, different packaging, so pick the extension your software actually asks for rather than assuming either will do. If you only want a viewable picture or a clip that plays anywhere, skip ahead to the last FAQ.
| Property | M2TS | MTS |
|---|---|---|
| Full name | BDAV MPEG-2 Transport Stream | MPEG-2 transport stream, AVCHD camcorder spelling |
| Where you see it | On a computer after import, and in Blu-ray disc structure | On the camcorder's SD card, written in-camera |
| Filename form | Long-filename .m2ts |
8.3 short name .MTS |
| Container as written here | BDAV framing — 188-byte TS packet + 4-byte timestamp header = 192-byte packets | Plain transport stream — 188-byte packets, sync byte at offset 0 |
| Video codec | H.264 / MPEG-4 AVC | H.264 / MPEG-4 AVC |
| Audio codec | Dolby AC-3 or linear PCM | Dolby AC-3 or linear PCM |
| Disc location | BDMV/STREAM/ on a Blu-ray; AVCHD/BDMV/STREAM/ on AVCHD media |
PRIVATE/AVCHD/BDMV/STREAM/ on the card |
| Typically associated with | Blu-ray authoring, computer playback/editing | Sony and Panasonic AVCHD camcorders (since 2006) |
| Best for | Importing into disc-authoring or editing software that wants .m2ts |
The raw recording straight off a camcorder |
Both extensions carry the same H.264 video; what changes is how that video is packetized. .m2ts is the spelling most editors and Blu-ray authoring tools expect, and the one this page writes with BDAV framing. Because the framing genuinely differs, renaming a file from one extension to the other relabels it without re-packetizing it — convert to the spelling you need instead.
.m2ts clips into its timeline..m2ts and refuses to recognize a .mts file.BDMV/STREAM/ layout and want the new still to match that extension..MTS — use CR2 to MTS so the extension matches the rest of the card..avchd/.mts spelling — use CR2 to AVCHD.The photo is rendered and packaged as a silent, single-frame AVCHD stream — the same H.264 video either extension carries, wrapped here in BDAV packets. Here is the before and after.
| Property | CR2 (source photo) | M2TS (output clip) |
|---|---|---|
| Type | Canon RAW still (unprocessed 14-bit sensor data) | Silent still-image AVCHD stream |
| Motion | Single frame | One rendered frame held for the "Image Duration" |
| Audio | None | None written (the container itself can carry AC-3 or PCM) |
| Resolution | ~20 MP | Downscaled to a 1080p-class HD target |
| Video codec | — (undeveloped RAW) | H.264 / MPEG-4 AVC |
| Aspect fill | — | "Background Color" letterbox bars (solid, never transparent) |
| Editing latitude | Full RAW (highlight recovery, white balance) | Baked in — none |
.cr2 onto the page or click "+ Add Files" to browse. You can queue several Canon photos at once.No — the video matches, the packaging does not. Render the same CR2 to each and the encoded H.264 frame is the same, but the transport stream around it is framed differently: .m2ts comes out BDAV-framed in 192-byte packets, each carrying a 4-byte timestamp header ahead of the 0x47 sync byte, while .mts comes out as plain 188-byte packets with that sync byte at the very start of the file. Those extra headers also make the .m2ts slightly larger for identical content. Renaming one to the other changes the label but not the packet framing — players that probe the stream usually cope either way, but a tool that strictly expects one framing will not accept the other. This page writes the BDAV-framed .m2ts that Blu-ray-authoring and editing tools expect; use CR2 to MTS if your software asks for .mts.
No on both counts. The converter renders your single CR2 to one still frame and holds that motionless frame on screen for the duration you set — there is no pan, zoom, or transition. It is also silent: a photo carries no audio, so there is nothing to encode, even though the M2TS container itself can carry Dolby AC-3 or linear PCM. If you upload several photos and choose "Merge images," they play back to back, each shown for its set duration — a sequence of stills, not a cross-faded slideshow. Add narration or music on your editing timeline after import.
Yes. A CR2 stores unprocessed 14-bit sensor data, which is why you can recover highlights and shift white balance long after the shot. To put the photo into a transport stream, the converter must develop it first — demosaicing the sensor data and baking in white balance, exposure, and tone — because a video stream has no concept of undeveloped RAW. Once that rendered frame is inside the M2TS, the latitude is gone, exactly as in a JPEG. Develop the RAW in a dedicated editor first if you want that control, and keep the original .cr2 as your master.
Lower than the photo, in practice. A 20-megapixel Canon sensor captures far more pixels than an HD video frame holds, so AVCHD/M2TS targets 1080p-class dimensions — choosing a 1920×1080 preset under "Video resolution" downscales the rendered image to fit. AVCHD was built around HD recording, so 1920×1080 is the natural target and detail beyond it is discarded — normal for putting a high-resolution photo into video. If preserving every pixel matters, keep the still as an image with CR2 to JPG instead of wrapping it in a video stream.
No. This is a file converter — it outputs a single rendered .m2ts stream, not the full BDMV/STREAM/ directory tree with the playlist (.mpls) and clip-information (.clpi) files a Blu-ray player or authoring tool reads. Building that structure is a disc-authoring task, much as a lone .m2ts is not a finished disc and a single .vob is not a finished DVD. Import the rendered clip into your Blu-ray-authoring or editing project, let that software lay it into the disc layout, and author from there. If your tool's dedicated AVCHD/Blu-ray importer doesn't see the loose file, use its generic file import instead.
Yes. Open Advanced Options and set "Merge strategy" to "Merge images" — every uploaded CR2 is rendered and placed in one M2TS, each still held for the "Image Duration" you set and playing back to back as a sequence (no cross-fade). Choose "Video per image" instead for a separate M2TS per photo. Either way the stream is silent and re-encoded to H.264; there is no remux path that keeps a photo as-is.
In our testing, a single full-resolution Canon CR2 held for 5 seconds at the "Very High" preset produced an M2TS only a couple of megabytes in size, because a motionless H.264 frame compresses heavily. Your file is uploaded over an encrypted connection, rendered and packaged into the M2TS on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.
For almost everyone, M2TS is the wrong target. If you only want a viewable, shareable picture, CR2 to JPG gives you a far smaller file that opens everywhere, and you keep the original .cr2 as your editable master. If you need a video clip for a modern editor, web upload, or phone playback, CR2 to MP4 carries the same H.264 in a container that plays natively almost anywhere, while M2TS does not. Reach for M2TS only when a specific Blu-ray-authoring or AVCHD-era workflow requires that exact container and extension.