Add your MTS file
Drop one or more .mts files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Grabbing a .jpg still from a .mts video is the quickest way to get a thumbnail, preview, or poster frame without opening an editor. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Grabbing a .jpg still from a .mts video is the quickest way to get a thumbnail, preview, or poster frame without opening an editor. An .mts file is AVCHD footage as written to a camcorder's memory card, containing H.264 video inside an MPEG transport stream. Sony and Panasonic camcorders from the late 2000s onward filled SD cards with .mts clips, so the extension is familiar to anyone importing family or event video.
A .jpg file is a photograph or other continuous-tone image compressed with the JPEG standard, the most widely used image codec ever shipped. Nearly every camera, phone, and website produces or accepts .jpg files, which makes it the default interchange format for photos. For this route the practical draw is opens everywhere, from 1990s software to the newest phone and excellent size-to-quality ratio for photographic content — balanced against every re-save re-compresses the image, so quality erodes across editing generations, which is worth knowing before you commit a large batch.
A still frame answers a different need than the video itself: thumbnails, link previews, cover art, and quick visual checks. Instead of screenshotting your player (which captures UI and compression artifacts at display size), this route decodes the actual .mts stream and hands you a clean .jpg at the video's native resolution — useful because opens everywhere, from 1990s software to the newest phone.
| Aspect | AVCHD video (.mts) | JPEG image (.jpg) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Lossy — discards detail it judges invisible to shrink files |
| How it stores data | uses 192-byte transport packets, standard 188-byte packets plus a 4-byte arrival timestamp, matching Blu-ray's BDAV layout | compresses 8x8 pixel blocks with a discrete cosine transform followed by quantization, which is where detail is discarded |
| Strongest at | importing camcorder footage into Premiere, Resolve, or Final Cut | publishing photographs on websites where file size and universal support matter |
| Weak spot | transport-stream packet overhead makes files larger than the same video in MP4 | every re-save re-compresses the image, so quality erodes across editing generations |
| Metadata | recording date, camera settings, and GPS coordinates on some models are stored in the AVCHD folder's clip-info files rather than in the .mts stream itself | carries EXIF (camera settings, GPS, orientation), XMP, and IPTC records in APPn marker segments, plus embedded ICC color profiles and thumbnails |
Drop one or more .mts files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .jpg in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if JPG is selectable, the route is real and validated.
Press Convert. A WebAssembly FFmpeg build decodes the opening video frame and encodes it as a still image without any upload.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid JPG file. Outputs keep the original filename with the .jpg extension.
You are extracting a single decoded frame from the mts stream, so the result is as sharp as the video itself at that instant. Choosing .png keeps it pixel-exact; .jpg and .webp apply mild, adjustable compression suited to sharing.
Yes — the .mts file is processed inside your browser tab and never uploaded. A WebAssembly FFmpeg build decodes the opening video frame and encodes it as a still image without any upload. Close the tab and the file is gone from memory.
JPEG is supported by every mainstream operating system, browser, image editor, and printer driver in use today. It decodes natively on iOS, Android, Windows, macOS, and Linux without any add-on codecs, and every browser has rendered it since the format reached the web in the 1990s.
A single .jpg frame is a tiny fraction of any video: expect kilobytes to a few megabytes depending on resolution, versus the megabytes-per-minute of the .mts source.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, recording date, camera settings, and GPS coordinates on some models are stored in the AVCHD folder's clip-info files rather than in the .mts stream itself; none of it is transmitted anywhere because the file never leaves your browser.