Convert MTS to MPG Online for Free

MTS to MPG Starts With What the Recipient Means by MPG

MTS is commonly the AVCHD camera-side extension for M2TS, a Blu-ray Disc Audio/Visual and AVCHD variation of MPEG-2 Transport Stream. It may contain AVC/H.264 camera video, audio, timestamps, and ancillary material. MPG is far less exact than it sounds. Microsoft documents that .mpg is used for MPEG-1 system streams and also frequently for MPEG-2 program streams. Both wrapper and coded-video expectations must therefore be stated before conversion.

Ask for a target profile, not an extension alone: MPEG-1 versus MPEG-2 program stream; video family, maximum size and rate; progressive or interlaced delivery; audio codec and layout; and the actual hardware or application. Microsoft also notes that systems with only an MPEG-1 video decoder cannot play MPEG-2 program streams without an additional MPEG-2 decoder. An MPG that opens in the conversion tool is not evidence that it meets a particular workstation, player, disc-authoring, or ingest requirement.

The result is an audiovisual derivative, not a complete camera master. Retain the MTS source and, where available, its AVCHD directory context. A broad MPG output may omit alternate audio, camera metadata, private data, captions, clip-spanning relationships, or other source-side information even though its selected video plays normally.

Why AVCHD Transport Stream Does Not Automatically Become MPG

Transport Stream and Program Stream are different MPEG systems choices. Both use packetized elementary streams, but Program Stream is designed for one program on relatively error-free storage such as a local file. Microsoft describes a multiplexer assigning each PES a one-byte stream ID. The Library of Congress describes program-stream PES packets as packs: a pack has a header followed by zero or more PES packets, with timing and bitrate information in its header.

A compatible remux changes this organization while retaining selected elementary streams. It is possible only when the output program-stream specification and receiver accept the existing coded video/audio. Many MTS clips are AVC/H.264 AVCHD recordings, while a conventional MPG requirement can expect MPEG-1 or MPEG-2 video. If that expectation differs, video is decoded and re-encoded rather than simply repackaged. Verify the actual source; an .mts name alone does not prove every video, audio, profile, or audio service.

Treat audio selection separately from multiplexing. Inspect every audio stream's codec, channels, sample rate, label, and audible role. Audition first, middle, and final landmarks. The first listed stream can be an alternate language, an audio-description service, or another non-primary role. Record which one is carried to MPG and why other streams are excluded. A technically clean target with an unintended soundtrack does not meet the request.

MPEG-1 and MPEG-2 Choices Change the Visual Result

The MPG extension creates a compatibility ambiguity that must be resolved through coded properties. Microsoft describes MPEG-1 as a progressive-video standard designed for Video-CD and CD-i contexts, commonly illustrated by 352 by 240 at 30 frames per second. That historical description is not a modern universal preset. An MPEG-2 program-stream target can use different frame rates and sizes, but the receiver still determines which profiles, bitrates, and audio combinations it accepts.

When AVC MTS footage is made into MPEG-1 or MPEG-2 video, the output is a fresh lossy generation. Higher target bitrate does not reconstruct detail already lost during source compression. Lower bitrate or an unsuitable encoder decision can make camera noise, grass, hair, water, titles, motion, and smooth gradients visibly fail in different ways. Compare moving footage, not just thumbnails, and retain the original rate and resolution only when that is actually permitted by the delivery spec.

Do not conflate codec choice with a better image. A DVD-style MPEG-2 target may be correct for an older workflow while a different receiver needs another profile. State exact properties in the manifest: coded video family, dimensions, nominal rate, rate-control policy, aspect signaling, and audio codec. This is more useful than telling a recipient the file is “high quality MPG.”

Fields, Cadence, and Display Shape Require a Deliberate MPG Policy

AVCHD camera material can be progressive, interlaced, or segmented-frame content. Field order is part of the moving image. An export that mistakes interlaced fields for progressive frames can show combing on motion; a deinterlacer can soften detail or create motion artifacts; an unnecessary frame-rate conversion can make pans judder. Preserve the source scan behavior when it is supported. If the MPG receiver requires a different form, document the field treatment, output cadence, and tool settings.

Pixel dimensions alone do not ensure correct display. Check display aspect ratio and pixel-aspect behavior in the required player. A 16:9 source encoded with incorrect signaling can appear squashed, and a 4:3 item can be stretched, even when a media inspector reports the expected width and height. Test a recognisable circular object, title-safe graphics, and full-frame movement after conversion.

Timing is another independent test. Compare first intentional picture/sound, a mid-program event, and final event against the chosen MTS stream. A constant shift can be a chosen trim or audio delay. Growing drift points instead to time-base, cadence, or processing trouble. Neither an MPG extension nor a bitrate setting resolves those causes.

MPG Audio Is a Receiver Contract, Not an Afterthought

The desired MPG video mode may constrain audio more tightly than the source camera does. Confirm allowed codec, rate, bitrate, channel layout, and track count. A converter that retains a source audio codec can make an efficient remux when it is accepted; otherwise it makes a new audio encode. That second encode cannot recover earlier discarded information, and an arbitrary downmix changes the programme. Test spoken consonants, music, effects, and the final decay, not only duration.

If multiple tracks are needed, establish whether the target program stream and player can select them as intended. Do not silently combine languages or commentary. When delivery truly requires a stereo fold-down, keep the mix decision in the manifest and listen for dialogue loss, phase cancellation, overload, or missing surround-derived cues. Captions and subtitles need their own planned representation rather than being assumed to travel with an MPG picture.

MTS Camera Material and MPG Delivery File Compared

Questions to Resolve Before Releasing an MPG File

Is MPG the same target as MPEG?
The extensions overlap in real use, but neither uniquely specifies MPEG-1 versus MPEG-2, program-stream behavior, or accepted codecs. Use the receiver's complete requirement.

Can the conversion avoid re-encoding?
Only when selected MTS streams are legal for the requested MPG program-stream output and the receiver accepts them. Inspect, remux, and test rather than guessing.

Why does this MPG look softer?
AVC-to-MPEG video conversion adds lossy coding, and bitrate, scaling, deinterlacing, or cadence changes can add their own artifacts.

Why is the image stretched?
Display/pixel aspect signaling is wrong or the receiver applies its own display rule. Check it on the actual endpoint.

What proves the handoff?
Independent stream inspection, three landmark comparisons, late seeking, required-receiver playback, and a manifest beside the retained MTS source.

Before delivery, verify the extension and actual program-stream mode, selected audio, coded video, frame/field behavior, duration, aspect ratio, and receiver playback. Keep the MTS source unchanged for future reprocessing.

A practical acceptance pass should deliberately force the edge cases an extension cannot describe. Open the output in a second parser and confirm the source video was not accidentally reduced to a thumbnail-sized preset, that the selected audio stream is the intended one, and that the reported aspect ratio corresponds to the displayed image. Play a high-motion section, pause on field-sensitive movement, and seek to a late scene. If a fault appears only after seeking, capture that timing and the receiving device name; it may be an index, multiplexing, or endpoint limitation rather than a visible encoding defect. Preserve that evidence with the versioned target settings so a corrected MPG does not have to be guessed from scratch.

For an MPEG-2 program-stream export, inspect the multiplexed output itself after encoding. Program streams use a one-byte PES stream identifier, so the receiving application should expose the deliberate audio/video services rather than an accidental duplicate or unwanted service. When an MPG has picture but no sound, or different sound after a seek, compare stream identification, codec acceptance, and the actual player before changing image settings. This is a container/receiver question, not proof that the camera audio is missing.