How to transcode AVCHD to MP4 for editing on Windows and Mac

AVCHD footage often arrives in .MTS or .M2TS files containing H.264 video and a separate compressed audio stream. The format was designed for consumer camcorders, so it is compact and dependable on the camera card, yet some editing timelines, browsers and review platforms handle it poorly. Converting to MP4 creates a more predictable working file while leaving the original recording untouched.

An AVCHD-to-MP4 conversion is not simply a file-extension change. The finished file needs a compatible video codec, an audio format the application understands and frame timing that matches the source. The practical workflow is to inspect each clip, choose between a fast remux and a full encode, select editing-friendly settings, then test the result before moving it into a larger timeline.

Pavtube gives Windows and Mac users a consistent place to convert, compress, mix and prepare AVCHD material. Adobe Media Encoder, Premiere Pro, HandBrake and FFmpeg can also perform the relevant jobs, although their controls differ. Whichever route you take, the important distinction is whether the editor needs quick compatibility or a lossless transfer of the original streams.

For Australian creators, frame-rate choices deserve particular care. Australia’s PAL background means 25p and 50p material is common, while imported Sony and Panasonic cameras may also record 50i, 29.97p or 59.94p. Footage of Sydney Harbour, Melbourne’s laneways or a drive along the Great Ocean Road should retain its native timing rather than being forced into a generic 30 fps setting.

Why AVCHD causes editing friction

AVCHD is often mistaken for a codec, but it is a recording format that can contain H.264 video, Dolby Digital audio and other compatible streams inside an MPEG transport stream. Changing .MTS to .MP4 without checking the contents does not make the streams more compatible. Some applications will open the renamed file but struggle with its audio, timestamps or interlaced fields.

A properly encoded MP4 with H.264 video and AAC audio offers broader support across Windows, macOS, Premiere Pro, iMovie and common media players. This reliability also matters when footage appears in browser-based campaign material, including promotional content for online games. DigiSNS’s online gaming resource represents another environment where compressed media must load consistently across different screens and connections.

Remuxing or re-encoding

Remuxing places the existing audio and video streams into an MP4 container without decoding and rebuilding them. It is fast, preserves the original quality and is worth testing first because there is no generational loss. The limitation is that MP4 compatibility is still not guaranteed if the source contains AC3 audio, interlaced video or unusual timestamps that the target editor rejects.

A full re-encode gives precise control over the frame rate, scan type, colour format, bitrate and audio layout. For a 1080p editing file, use H.264 at 1920 × 1080, 8-bit 4:2:0 colour and a matching frame rate, with AAC stereo audio at 48 kHz and 192–320 kbps. An encoder quality value around CRF 18–20 or a 15–25 Mbps target is suitable for intermediate footage. General advice on selecting a repeatable toolchain appears in these practical workflow notes.

Preparing sources and choosing settings

Copy the camera card contents to a working drive and keep the originals read-only. Before importing, inspect the resolution, frame rate, bitrate, field order and audio channels. MediaInfo, FFprobe or a good player can display this information. Renaming a file cannot repair a damaged recording, and a copy on the computer’s SSD will be much faster than reading directly from the card during editing.

Keep progressive footage progressive. For a true 50i source, use a suitable deinterlacer and choose either 25p for a conventional timeline or 50p when the motion and delivery requirements justify retaining twice as many frames. Australian crews commonly need 25p or 50p versions for broadcast, social and client-delivery work, so the original timing should guide each decision. A 1080p AVCHD recording at roughly 24 Mbps uses about 1.8 GB for every ten minutes, which is useful when planning SSD, backup and cloud-review capacity.

Decide whether the MP4 will be an editing master, a review copy or the final online deliverable. Intermediate files should retain enough detail for grading and motion-heavy timelines, while web copies can use a lower bitrate and smaller dimensions. Preserve a stereo mix for ordinary social-media projects, but retain the surround channels when the finished film requires them. Australian productions moving between local teams, agencies and remote reviewers often benefit from keeping both a high-quality master and a lightweight H.264 version.

Converting footage on Windows

Install Pavtube and create an output folder on an SSD rather than placing converted files beside the source card. Add the .MTS or .M2TS clips, select MP4 as the container and choose H.264 for video with AAC for audio. Confirm the dimensions, frame rate and deinterlacing option before starting a batch. Adobe Media Encoder and HandBrake are alternatives when detailed bitrate controls or Adobe-specific presets are required.

Hardware acceleration through NVENC, Intel Quick Sync or AMD AMF can reduce conversion time, but software encoding usually produces better results at the same file size. Use hardware encoding for quick review copies and high-quality software encoding for final editing masters or archival derivatives. Let the first short clip finish before processing an entire shoot, then confirm that the laptop has enough free space, a stable power connection and a drive capable of sustaining the write speed.

Converting footage on Mac

Pavtube follows the same general process on macOS: import the AVCHD files, choose MP4 with H.264 and AAC, verify the source frame rate and start the batch. Adobe Media Encoder offers deeper control inside Premiere Pro workflows, while HandBrake provides a straightforward standalone option. Keep the destination on local storage, name files consistently and avoid ejecting the camera card until the originals have been verified and backed up.

FFmpeg is useful when the metadata needs checking or when a scripted batch offers more control. The following commands inspect a source, remux it without re-encoding and then create a conventional editing file:

ffprobe -i input.MTS
ffmpeg -i input.MTS -map 0 -c copy -movflags +faststart output.mp4
ffmpeg -i input.MTS -c:v libx264 -preset slow -crf 18 -pix_fmt yuv420p -c:a aac -b:a 192k -movflags +faststart output.mp4

Add a deinterlacing filter only when the source has been confirmed as interlaced. Apple Silicon systems can also use VideoToolbox for faster encoding, although software x264 generally remains preferable for a high-quality intermediate master.

Checking the finished MP4

Open the converted file in the editor where it will actually be used, then play it from beginning to end. Scrub across cuts, inspect the first and last frames and listen for synchronisation problems. Check for dropped frames, clipped audio, incorrect colours and black frames. Comparing the MP4 with the source on the same display can reveal changes that a quick preview on a phone would miss.

If playback stutters, increase the bitrate rather than repeatedly lowering the resolution. Audio that the editor cannot decode should be converted to AAC, while irregular timing may require a complete re-encode instead of a remux. Keep the original files, the converted editing copies and separate delivery exports in clearly organised folders. The step-by-step editing guide provides a useful reference for checking compatibility before a production timeline expands with hundreds of clips.