Initializing... drag & drop files here
Supports: MXF
MXF is the SMPTE-standardised wrapper that broadcast and post-production systems hand around — a mastered clip, often at a mezzanine bitrate, sometimes hours long. EPS is a single page of PostScript describing a single picture. Nothing about those two formats overlaps except that both can hold an image, so this conversion does the only sensible thing: it pulls one frame out of the MXF and writes it into an Encapsulated PostScript file that a page-layout application will place.
The reason this page exists rather than a one-line tool blurb is that the EPS extension misleads people in two directions at once. It is a vector format, but nothing here is vectorised. And it is a "print" format, but the file it produces is enormous and only 72 pixels per inch. Both facts are measurable, and both are below.
The job runs in two stages on our servers. First the MXF is decoded and one frame is written out as a lossless PNG — no quality setting is involved at that step, so nothing is lost beyond what the MXF's own codec already discarded. Then that PNG is handed to ImageMagick, which embeds it inside an EPS at a fixed density of 72 pixels per inch with metadata stripped, and takes frame 0 of the intermediate explicitly so that the declared output path is the file you get.
That density is not cosmetic. Pinning it at 72 makes one pixel map to exactly one PostScript point, which is why the bounding box in the output matches the frame dimensions in pixels. It is also why there is no DPI control on this page: changing it would break the correspondence the converter deliberately establishes.
.mxf onto the page or click "Add Files". Several files can be queued and they all run with the same settings. MXF masters are frequently several gigabytes, so this step normally takes far longer than the conversion — if you only need one still, cut a short section first with the Video Cutter, which accepts .mxf directly.0. Type the moment you want; decimals are accepted, and we confirmed that seeking to a non-zero time on an MXF returns a genuinely different frame rather than the opening one. Switching to Multiple Screenshots samples the whole clip at a Capture Rate instead, which opens at "1 second per frame" and ranges from ten frames a second down to one frame every ten seconds..eps. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.We converted a 640 × 360 frame from a test .mxf and read the result byte for byte. The header explains the file size on its own:
%!PS-Adobe-3.0 EPSF-3.0
%%Creator: (ImageMagick)
%%BoundingBox: -0 -0 640 360
%%DocumentData: Clean7Bit
%%LanguageLevel: 1
%%Pages: 1
| Property | Value in our test output |
|---|---|
| Header | %!PS-Adobe-3.0 EPSF-3.0 |
| Producer | ImageMagick |
| PostScript language level | 1 |
| Image data encoding | ASCII hexadecimal (Clean7Bit) — no binary, no compression |
| Bounding box | 0 0 640 360 — one pixel maps to one PostScript point |
| Effective resolution | 72 DPI, fixed; no DPI control exists on this page |
| Pages | 1 |
| Vector content | None — the frame is embedded as a raster image |
| Size for the 640 × 360 frame | 1,405,821 bytes |
That is 6.10 bytes on disk per source pixel, and the relationship is linear in pixel count. Three properties of the encoder drive it: PostScript Level 1 with no image compression, Clean7Bit ASCII-hex data at two text characters per byte of pixel data, and no downsampling of the frame on the way in.
Resolution Percentage is therefore the only lever that matters, and it is an effective one. Measured on the same frame:
| Resolution Percentage | Output pixels | Bounding box | File size |
|---|---|---|---|
| Keep original | 640 × 360 | 0 0 640 360 | 1,405,821 bytes |
| 80 (the value the control opens at) | 512 × 288 | 0 0 512 288 | 901,775 bytes |
| 50 | 320 × 180 | 0 0 320 180 | 355,727 bytes |
| 25 | 160 × 90 | 0 0 160 90 | 93,199 bytes |
Halving the dimensions quarters the pixel count and very nearly quarters the file. Scale up from the per-pixel figure for larger frames: a 1280 × 720 frame lands near 5.6 MB and a full 1920 × 1080 frame near 12.6 MB.
MXF files usually arrive from an ingest, a playout server or an NLE export, which means they tend to be long, high-bitrate, and named after a job rather than their content. Two habits make this conversion much less painful.
Find the timestamp somewhere else first. VLC, mpv and any NLE will open an MXF and show you a clock; note the moment you want and type it into Time (seconds). Guessing and re-uploading a multi-gigabyte master is the slow path.
If you genuinely do not know where the shot is, use Multiple Screenshots at a coarse rate — one frame every five or ten seconds — to get a contact sheet's worth of EPS files, pick the one you want, then run the job again with Specific Frame at that exact time. Do not start at ten frames a second: at 6.1 bytes per pixel, every sampled frame is its own multi-megabyte file, and a minute of HD footage sampled that fast would produce hundreds of megabytes of PostScript.
No. The frame is embedded inside the EPS as a raster image with a bounding box drawn around it — an EPS is a PostScript program, and this one simply paints a bitmap. Enlarging it in a layout application enlarges pixels exactly as it would with a JPEG. Real vectorisation would need either the original vector artwork or a deliberate tracing tool, and tracing photographic or video content almost never produces usable results anyway.
Because the MXF is compressed and the EPS is not. Our measured output is 1,405,821 bytes for a 640 × 360 frame — 6.10 bytes per source pixel — and there is no compression setting anywhere on the page that changes it. The encoder writes PostScript Level 1 image data in ASCII hexadecimal, so every byte of pixel data becomes two text characters before any structural overhead. Only Resolution Percentage reduces the size, and it does so predictably: 50 gives you roughly a quarter of the bytes.
It prints exactly the detail the video frame contained, at 72 pixels per inch of placed size. Because one pixel becomes one point, a 640 × 360 frame arrives in a layout at 640 × 360 points — 8.9 × 5 inches — with only 72 samples per inch behind it, which is well short of any print standard. Scale it down in the layout application to raise the effective resolution. A video frame is simply not a high-resolution source, whatever container you put it in.
Because neither would have anything to act on. The EPS branch of the converter writes image data without lossy compression, so there is no quality value, and it pins the density at 72 with the units set to pixels-per-inch specifically so that one pixel equals one point and the bounding box matches the frame's pixel dimensions. Image resolution — Keep original or Resolution Percentage — is the entire control surface here, and that is a deliberate choice rather than a missing feature.
Both are discarded. An EPS holds one page of PostScript describing one picture; there is nowhere in the format for an audio track, a timecode track, or the descriptive metadata an MXF wraps around its essence. The conversion also strips metadata from the intermediate image on the way out. If you need the soundtrack, run the same master through an audio conversion as a separate job, and keep the original .mxf if the timecode matters.
Yes, by sampling rather than exporting exhaustively. Multiple Screenshots offers a Capture Rate from one frame every ten seconds up to ten frames per second, and each sampled frame becomes its own .eps. Do the arithmetic before you choose: at HD resolution each file is several megabytes, so anything faster than one frame every few seconds produces an unmanageable pile very quickly.
Trim first. The Video Cutter accepts .mxf and lets you keep only the section you care about, which turns a multi-gigabyte upload into a small one. The conversion itself is quick; the upload is what costs you time, because the work runs on our servers rather than on your own machine.
Use EPS only when the receiving application specifically asks for it — some print workflows and older page-layout templates still do. For anything else MXF to PNG gives you the same picture, losslessly, in a file a fraction of the size, and MXF to JPG is smaller again where a little compression is acceptable. Both place into modern layout tools without complaint.
The .mxf is uploaded over an encrypted connection, decoded on our servers, and both the upload and the resulting .eps are deleted automatically after a few hours. Files are never shared or made public, no watermark is added, and no account is needed. Because the processing happens server-side, the practical constraint on a large master is upload size and time rather than anything about your own hardware.