Initializing... drag & drop files here
Supports: MXF
2.100 = 2.1 s) to grab a single still, or "Multiple Screenshots" to sample at fixed intervals from every 1/10 second up to every 10 seconds across the whole clip.MXF (Material Exchange Format) is the SMPTE ST 377-1 wrapper used by broadcasters, post houses, and Avid Media Composer to carry professional essence with full timecode and metadata. PPM (Portable Pixmap, part of the Netpbm family) is the opposite end of the spectrum: a header-plus-raw-RGB file with no compression, no color profile, and no alpha — exactly what image-processing code wants to read.
cv2.imread), Pillow, scikit-image, or custom CUDA kernels without a decoder bug surface.If you need a smaller file for distribution rather than analysis, use MXF to PNG (lossless compressed) or MXF to JPG. To rewrap MXF for general playback, see MXF to MP4.
| Property | MXF | PPM |
|---|---|---|
| Type | Video/audio container | Single-image raster |
| Standard | SMPTE ST 377-1 (2004, revised 2019) | Netpbm informal spec (1988+) |
| Compression | Codec-dependent (DNxHD, AVC-Intra, MPEG-2, IMX) | None (raw RGB) |
| Bit depth | 8, 10, or 12 bit per channel (codec-dependent) | 8 or 16 bit per channel |
| Alpha channel | No (use separate matte track) | No (use PAM/PNG for alpha) |
| Metadata | Rich — timecode, KLV, multi-track, descriptors | Minimal — # comment lines only |
| File size (1080p, single frame) | ~50-300 KB depending on codec | ~6.2 MB (8-bit) / ~12.4 MB (16-bit) |
| Magic header | 06 0E 2B 34 02 05 01 01 (KLV) |
ASCII P6 (binary) or P3 (plain) |
| Typical software | Avid Media Composer, DaVinci Resolve, FFmpeg, bmx | OpenCV, ImageMagick, GIMP, Pillow, FFmpeg image2 |
| Variant | Magic | Bit depth | 1080p frame size | When to pick |
|---|---|---|---|---|
| Binary RGB (P6) — default | P6 |
8-bit (maxval 255) | ~6.2 MB | Standard pipelines; what most readers expect |
| Binary RGB (P6) 16-bit | P6 |
16-bit (maxval 65535) | ~12.4 MB | HDR/grading reference; preserves 10-12 bit codec headroom |
| Binary bitmap (PBM, P4) | P4 |
1-bit | ~0.25 MB | Masks, thresholded silhouettes, document OCR pre-processing |
Note: this converter writes binary P6 PPM. If you need the ASCII P3 variant for hand-inspection, run the output through pnmtoplainpnm or open in any Netpbm tool.
MXF wraps a compressed codec (DNxHD HQ runs around 145 Mb/s for 1080p, AVC-Intra 100 around 100 Mb/s); PPM is uncompressed. A single 1920×1080 8-bit P6 frame is 1920 × 1080 × 3 = 6,220,800 bytes plus a tiny header. So a 10-second clip that fits in ~180 MB of MXF expands to roughly 1.5 GB of PPM at 24 fps. That's expected — pick "Specific Frame" if you only need stills, or downscale via Resolution Percentage.
Pick 8-bit unless you specifically need more precision. Most viewers and many libraries (Pillow's older PPM reader, some image-processing examples) only handle 8-bit cleanly. Choose 16-bit when the MXF source is a 10-bit codec (DNxHD HQX, AVC-Intra 100/200, XDCAM 422) and you're feeding the data into color science, HDR analysis, or a pipeline that will redither later — going to 8-bit early throws away the codec's headroom.
Both are the Portable Pixmap from the Netpbm family. P6 (binary) stores each pixel as raw bytes — compact and what FFmpeg, OpenCV, and ImageMagick produce by default. P3 (plain) stores each RGB triplet as decimal ASCII numbers separated by whitespace — human-readable but typically 3-5× larger. This tool outputs P6; convert to P3 with pnmtoplainpnm or convert in.ppm -compress none out.ppm (ImageMagick) if you need the ASCII form.
Yes. PPM is well-supported by image-processing tools (ImageMagick, GIMP, IrfanView, Photoshop with a plugin, every Netpbm utility, OpenCV, Pillow) but is not a web-deliverable format — browsers and Windows/macOS Photos won't render it. If you need to share or preview the frame, run a second pass to PPM to PNG or PPM to JPG after extraction.
The interval selector is time-based (every 1/10 s up to every 10 s). For exact frame-cadence extraction (e.g. every 5th frame) the cleanest workflow is to grab one frame per frame interval (every 1/24 s for 24p source, every 1/25 s for 25p PAL, every 1/30 s for NTSC 29.97) and then keep every Nth output file. For dense sampling on long clips, also consider lowering the resolution preset — six megabytes per frame adds up fast.
No. PPM only supports # comment lines in its header — no timecode, no XMP, no ICC profile. The file name carries the extraction ordinal (e.g. clip-0001.ppm, clip-0002.ppm). If you need to preserve the source timecode, capture the start timestamp from the "Specific Frame" input and multiply by your sampling rate to reconstruct, or extract to MXF to TIFF instead — TIFF preserves embedded metadata tags.
The converter ingests SMPTE ST 377-1 OP-Atom and OP1a operational patterns wrapping common essence codecs: Avid DNxHD/DNxHR (VC-3), Panasonic AVC-Intra (50/100/200), Sony XDCAM HD and XDCAM HD422, Sony IMX (D-10) MPEG-2 4:2:2, Long-GOP MPEG-2, and DV/DVCPRO. P2 MXF and XDCAM EX clip-wrapped variants also load. If a clip refuses to import, it's usually an exotic essence (JPEG 2000 in MXF-IMF or a proprietary Avid track) — try rewrapping to MP4 first via MXF to MP4.
Yes. Drag in multiple files; each is processed independently and you can apply the same Frame Selection and Bit Depth to all of them. For long-form material — a 60-minute MXF news package — pair "Multiple Screenshots" with a coarse interval (every 5 or 10 seconds) and a 480p resolution preset so the resulting PPM sequence stays manageable on disk.
The browser handles upload directly to processing, so the practical ceiling is your available RAM and browser memory — typically several GB of MXF works without issue on a modern desktop. There's no enforced free-tier cap of the kind cloud converters impose, and no watermark on the output.