Initializing... drag & drop files here
Supports: BMP
.MTS is the file that a consumer HD camcorder writes to its memory card: an MPEG-2 transport stream carrying H.264 video, defined by the AVCHD specification. .BMP is the opposite kind of file — a single uncompressed Windows bitmap with no timeline, no codec and no audio. Converting one into the other means synthesising a short clip: your still is held on screen for a set number of seconds, encoded as H.264, and muxed into a transport stream so an AVCHD-oriented editor or player will accept it alongside real camera footage. This page documents both formats and the settings that matter.
| Property | Value |
|---|---|
| Full name | Windows Bitmap / device-independent bitmap (DIB) |
| Defined by | Microsoft, as part of the Win32 GDI documentation |
| File structure | BITMAPFILEHEADER, then a BITMAPINFOHEADER (or BITMAPV4HEADER / BITMAPV5HEADER), an optional RGBQUAD colour table, then the pixel array |
| Compression | Normally none (BI_RGB); an optional run-length encoding exists for indexed images but is rarely seen |
| Bit depths in common use | 1, 4 and 8 bpp (palette-indexed), 16, 24 and 32 bpp (direct colour) |
| Row storage | Each row is padded so its stride is a whole number of 4-byte DWORDs |
| Row order | Bottom-up when the header's height is positive; top-down when it is negative |
| Transparency | Only via the later BITMAPV4HEADER / BITMAPV5HEADER alpha mask; ordinary bitmaps are fully opaque |
| Audio / timeline | None — one static image, nothing else |
| Property | Value |
|---|---|
| Full name | AVCHD stream file, written as .MTS on camera media and .M2TS on disc |
| Defined by | The AVCHD specification, whose official format site has been maintained by the AVCHD Format Co-Promoters since 2006 |
| Container | MPEG-2 Transport Stream |
| Video codec | MPEG-4 AVC / H.264 |
| Audio codecs in the spec | Dolby Digital (AC-3) at 64-640 kbps, or Linear PCM at 1.5 Mbps for two channels |
| Where you normally find it | AVCHD/BDMV/STREAM on a camcorder's SD card or internal memory |
| Native browser playback | None — .mts is not an HTML5 <video> format |
| Best for | Feeding an AVCHD-aware editor or camcorder workflow that rejects loose image files |
| Practical alternative | MP4, which uses the same H.264 video in a container everything understands |
.bmp onto the page or click "+ Add Files". With more than one bitmap, Merge strategy decides the outcome: Merge images produces a single .mts containing every still in order, Video per image produces one file each..mts. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.No. A bitmap has no audio to carry, so the encoder writes a video-only transport stream. In our testing, a 1920 x 1080 bitmap converted with the default 5-second duration produced a file that ffprobe reports as format_name=mpegts with a duration of 5.000000 seconds and exactly one stream, codec_type=video. That matters if your editor expects paired streams: some AVCHD-oriented tools will import a video-only .mts happily, while others expect the AC-3 or Linear PCM track the AVCHD spec describes. If your editor refuses it, the reliable fix is to import an MP4 instead and let the editor generate silence on the timeline.
H.264 / MPEG-4 AVC, which is the codec the AVCHD specification calls for. The Video Codec control also lists H.265, MPEG-1, MPEG-2, MPEG-4, DivX and Xvid, but anything other than H.264 stops the file being AVCHD-conformant even though the transport stream will still mux and play in VLC or mpv. Leave it alone unless you have a specific reason.
They are the same transport-stream format with different filename conventions. Camcorders writing to their own media use .MTS inside the AVCHD/BDMV/STREAM folder; the same streams copied into a Blu-ray disc structure are named .M2TS. Renaming one to the other does not change the bytes, and both carry H.264 in an MPEG-2 transport stream. Our output is a transport stream, so if a specific tool insists on the .m2ts suffix, renaming is usually enough.
The common case is inserting a title card, a slate, a logo, or a scanned document into an existing AVCHD project without leaving the camcorder-native workflow. Some older camera-companion and disc-authoring applications only ingest what they recognise as camera footage and simply ignore loose .bmp or .jpg files in the same folder. Producing a short, conforming clip sidesteps that restriction. If you are editing in a modern NLE that accepts images directly, you do not need this conversion at all.
Not exactly. H.264 is a lossy codec working in a chroma-subsampled YUV colour space, so a 24-bit RGB bitmap is converted before encoding and fine colour transitions are approximated. Photographic content survives this very well at the default "Very High" preset. Screenshots, UI captures, text and hard-edged line art are the hard cases: chroma subsampling softens coloured edges regardless of bitrate. If pixel fidelity matters more than having a video file, keep the image as an image with BMP to PNG, which reproduces the source exactly at the Highest preset.
Because the bitmap's aspect ratio does not match the video frame you asked for. Rather than stretching your picture, the encoder centres it and pads the leftover area with the Background Color, which opens on White. Change that swatch to match your artwork, or set Video resolution to Keep original so the frame takes the bitmap's own dimensions and no padding is needed at all. AVCHD-conformant playback devices generally expect standard HD frame sizes, so if the file has to be device-legal, keep 1920 x 1080 and accept the bars.
Yes. Upload them together and choose Merge images; each still is held for the Duration you picked and they play back in order as a single clip. Runtime is the image count multiplied by the duration, so eight stills at 5 seconds each give a 40-second file. Choose Video per image if you would rather have one .mts per bitmap — useful when each clip is going to a different point in a timeline.
No, and no video format could keep it. Alpha described by a BITMAPV4HEADER or BITMAPV5HEADER is flattened during encoding, and the area that was transparent takes the Background Color instead. This is worth planning for: a logo cut out on transparency will arrive on a solid white rectangle unless you change that swatch first. If you need the transparency preserved, convert to an alpha-capable image format such as PNG or WebP instead.
MP4 is the better default. Both carry H.264 video, but MP4 plays in browsers, on phones, in every editor and on every streaming target, while .mts only makes sense when something downstream specifically expects AVCHD structure. Convert to BMP to MP4 unless a camcorder-native tool or disc-authoring chain has told you otherwise. If you already have camera .mts footage you want in a friendlier container, MTS to MP4 handles that direction.