Convert MTS to MPEG Online for Free

MTS to MPEG Changes the Delivery Container, Not Just the Suffix

An MTS file is commonly the AVCHD camera-facing name for M2TS material: a Blu-ray Disc Audio/Visual and AVCHD modification of MPEG-2 Transport Stream. It can multiplex AVC/H.264 video, audio, timestamps, and related streams. An MPEG output normally means an MPEG-1 or MPEG-2 system/program stream, often saved with the .mpeg extension. The two files may both belong to the MPEG family, but their stream organization and expected playback environments are different.

First identify the requested target precisely. “MPEG” does not promise one video codec, one audio codec, or one receiver behavior. Microsoft documents that both MPEG-1 system streams and MPEG-2 program streams commonly use .mpg or .mpeg; older Windows installations can require an additional MPEG-2 decoder for MPEG-2 program streams. A filename change cannot satisfy such a request. Decide whether the recipient needs a genuine MPEG-1 system stream, MPEG-2 program stream, or a codec-specific preset before starting.

Keep the original MTS and its camera folder structure where it exists. The converted MPEG is a derivative delivery copy: it does not automatically retain every alternate audio track, subtitle, private-data element, chapter relationship, or camera metadata. Record the source identity and the target profile so the file is not later treated as an archival substitute for the acquisition material.

Transport Packets and Programme Packs Solve Different Problems

MPEG-2 Transport Stream and Program Stream are separate systems coding options, although both are built from packetized elementary streams (PES). The Library of Congress describes Program Stream as combining one program's elementary streams in a single stream, with multiplexing information for synchronized presentation. Its PES packets are organized in packs. Each pack has a pack header followed by zero or more PES packets; the header carries timing and bitrate information, and an MPEG-2 pack header begins with 0x000001BA.

That distinction is why MTS-to-MPEG can be a remux only in a narrow case. If selected source streams and their coded properties are accepted by the chosen program-stream target, the operation can reorganize them without re-encoding. But AVCHD MTS footage commonly contains AVC video and codec/profile combinations that a requested MPEG program-stream workflow or legacy player may not accept. A converter then decodes and re-encodes one or more streams. Inspect the actual video codec, profile, frame size, rate, field order, audio codec, channels, and all track identities before choosing either path.

Do not borrow a transport-stream “first PID” rule to select audio. A camera clip can have more than one audio service, and stream order is not an editorial choice. Audition the opening, a middle landmark, and the end for each candidate. Write down the selected stream, language or role where known, and whether the target intentionally excludes alternate audio. A valid MPEG with commentary instead of production sound is still the wrong deliverable.

Choose the MPEG Video and Audio Profile From the Receiver

Programme stream is a wrapper decision, not a quality promise. MPEG-1 targets have historically used progressive video around Video-CD-style constraints, while MPEG-2 program streams are widely associated with DVD and SVCD use. Neither statement makes every codec combination under a broad .mpeg extension interoperable. Get the receiver's required video family, maximum frame size, frame rate, field order, aspect signaling, bitrate policy, audio codec, audio rate, and channel layout in writing.

If AVC camera video must become MPEG-2 video, it is a new lossy video generation. Encoding at a high rate cannot recreate detail removed in acquisition compression, and a lower target rate can expose mosquito noise, block edges, banding, or smeared fine texture. Examine foliage, water, text, rapid pans, low-light noise, and saturated gradients rather than relying on a still frame. If the delivery accepts the original coded video in a compatible wrapper, a tested remux may avoid this loss; it still does not make the result universally playable.

Audio deserves an independent decision. A target may specify MPEG audio Layer II, AC-3, or another allowed choice. Re-encoding an already lossy camera soundtrack adds another generation. Preserve sample rate and channel intent when accepted; a stereo fold-down or 5.1-to-stereo mix is editorial work. Check dialogue, transient effects, music, and the final tail after conversion, and label a changed mix honestly.

Interlacing, Frame Rate, and Presentation Timing Need Separate Tests

Many AVCHD-era cameras record interlaced or segmented-frame material. Field order, cadence, and frame-rate conversion are not cosmetic settings. If an interlaced source is encoded or flagged as progressive without correct processing, motion can show combing; an unsuitable deinterlace can reduce vertical detail or create motion artifacts. Retain the source scan characteristics when the receiver accepts them, or document the deinterlacer, output cadence, and intended display when it does not.

Compare presentation rather than only file duration. Program-stream packs and PES timing permit synchronized output, but a converted file can still begin late, lose a final frame, drift, or select the wrong range. Test the first intentional image and sound, one recognizable middle event, and the ending against the MTS. A fixed offset can be a trim or delay choice; a growing mismatch needs a time-base, rate, or processing diagnosis. Bitrate changes cannot fix those faults.

Check displayed aspect ratio as well as stored pixels. A 16:9 camera image delivered with incorrect aspect signaling can look squeezed even when the frame dimensions look plausible in an inspector. Validate on the actual receiver where possible, including a seek to a late point and a pause on moving detail.

What the MPEG Conversion Preserves, Omits, or Rebuilds

A successful video decode does not prove a complete transfer of meaning. MPEG program-stream delivery can retain the selected video and selected audio with synchronization, but it does not inherently carry the camera's AVCHD directory relationship, every private stream, all alternate tracks, or the source's editing provenance. Captions and associated data need their own verified transfer plan. Preserve them externally when the target does not define a supported representation.

Build a compact manifest: source filename and checksum, selected video/audio tracks, source codec properties, target program-stream and codec choices, frame and aspect behavior, audio layout, any trim/deinterlace/resample/downmix operation, output duration, and tested device or application. That record makes later faults actionable. It distinguishes an intended MPEG-2 delivery encode from a mistaken assumption that a file named MPEG is equivalent to the original MTS camera asset.

MTS Acquisition and MPEG Programme Delivery Compared

MTS to MPEG Questions That Affect a Real Handoff

Is changing .mts to .mpeg enough?
No. The systems layer, codecs, and receiver acceptance must be verified; renaming does not remux or transcode anything.

Can this be lossless?
Only a compatible stream copy/remux avoids a new encode. AVC-to-MPEG-2 or any audio recode is lossy, even when the output uses a large bitrate.

Why does the MPEG play without audio?
The selected audio codec, sample rate, channel layout, or multiplexing may not be supported by that receiver. Inspect the file and test the receiver's documented target profile.

Why is moving footage combed or jerky?
Field order, interlacing, deinterlacing, or frame-rate conversion was handled incorrectly. Compare the source scan behavior and re-export with a documented policy.

What must be retained after delivery?
The MTS source, related camera/AVCHD assets, captions or alternate tracks, conversion manifest, and tested MPEG output.

Before release, reopen the MPEG independently, verify its program-stream and coded properties, compare three source landmarks, inspect audio-track selection and aspect behavior, seek late in the programme, and play it on the required receiver.

One final technical check is worth making before a batch delivery: distinguish a correctly multiplexed program stream from a merely decodable file. Confirm the output's declared codec and stream arrangement with an independent inspector, then run it through the expected receiver from the beginning and after a late seek. Look for missing audio after a picture change, a black first frame, aspect-ratio switching, field artifacts during a pan, and a truncated final GOP. If any of these occur, report the exact landmark and target profile rather than applying an unrelated bitrate increase. The original MTS, a tested MPEG, and a specific manifest make the corrective pass reproducible.