Initializing... drag & drop files here
Supports: F4V
This pulls one frame out of an Adobe F4V video and writes it as an Encapsulated PostScript file. The word "PostScript" leads people to expect vector artwork, so the most important thing to say up front is that no tracing or vectorisation happens here. The output is your video frame, pixel for pixel, embedded inside a PostScript program that draws it. That is a legitimate and long-established thing to do — it is how you get a raster image into a print or typesetting workflow that only accepts EPS — but it means the file is large and cannot be scaled up without softening. This page gives the exact structure, the size arithmetic and the page geometry.
Read from a file we produced from a 1920 × 1080 frame:
| Header line | Value |
|---|---|
| Format declaration | %!PS-Adobe-3.0 EPSF-3.0 |
%%LanguageLevel |
1 — the original PostScript language level, with no compression filters |
%%DocumentData |
Clean7Bit — the image is written as ASCII hexadecimal, not binary |
%%BoundingBox |
0 0 1920 1080 |
%%HiResBoundingBox |
0 0 1920 1080 |
%%Pages |
1 |
| Image content | One embedded raster, drawn by a PostScript colour-image operator |
Two consequences follow from LanguageLevel: 1 plus Clean7Bit. There is no compression at all — Level 1 EPS predates the filters later PostScript versions use — and every byte of image data is written as two ASCII hex characters, so the pixel data alone occupies twice what the raw samples would. That is why these files are the size they are.
.f4v onto the page or click "+ Add Files"; several can be queued and each produces its own EPS. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.0, which takes the opening picture. The field accepts decimals, so 47.25 lands forty-seven and a quarter seconds in. Switching to "Multiple Screenshots" samples the whole video at a Capture Rate you pick, from one frame every 0.1 s to one every 10 s, and writes one EPS per frame.The converter pins the resolution at 72 pixels per inch, which in PostScript units means one pixel becomes exactly one point. The bounding box therefore equals the frame size in points, and the printed dimensions follow directly:
| Frame size | EPS size (measured) | Bytes per pixel | Page size at 1 px = 1 pt |
|---|---|---|---|
| 640 × 360 | 1,405,825 bytes | 6.10 | 8.89 × 5.00 in (225.8 × 127.0 mm) |
| 1280 × 720 | 5,606,200 bytes | 6.08 | 17.78 × 10.00 in (451.6 × 254.0 mm) |
| 1920 × 1080 | 12,606,811 bytes | 6.08 | 26.67 × 15.00 in (677.3 × 381.0 mm) |
Roughly six bytes per pixel is the constant to plan around: three colour samples written as six hex characters, plus line breaks and the PostScript preamble. A 1080p frame is therefore always around 12.6 MB regardless of what it shows, because uncompressed formats do not care about content.
The page-size column matters if the EPS is going into a layout. A 1080p still is placed at 26.67 inches wide by default, which is far larger than any normal page — you scale it down in the layout application, and doing so raises the effective resolution rather than lowering it. Placed at 8 inches wide, that same 1920-pixel frame prints at 240 dpi, which is respectable.
| Property | Value |
|---|---|
| Full name | Flash MP4 Video |
| Introduced with | Flash Player 9 Update 3 (9.0.115.0), released 3 December 2007 |
| Container | ISO base media file format — the same family as MP4 |
| Typical video codec | H.264 / MPEG-4 AVC |
| Typical audio codec | AAC |
| Relationship to FLV | The replacement for it; FLV used Sorenson Spark or VP6 in Adobe's own container |
| Status | Superseded by plain MP4 after Flash Player's retirement on 31 December 2020 |
Because F4V is ISO base media file format underneath, the audio track is decoded and discarded here without difficulty — an EPS holds a single still image and nothing else.
No, and nothing on this page will make it one. The conversion embeds your video frame as a raster inside a PostScript wrapper; there is no tracing, no edge detection and no path generation. Scaling the placed image up will soften it exactly as it would with a JPEG. If you genuinely need vector paths, that is a tracing job in a drawing application working from a clean still, and a compressed video frame is a poor starting point for it.
Because Level 1 PostScript has no compression and the data is written as ASCII hexadecimal. Each colour sample becomes two text characters, so three bytes of pixel become six characters — around six bytes per pixel in practice once line breaks and the preamble are counted. A 1920 × 1080 frame is 2,073,600 pixels, which lands close to 12.6 MB every time. If size is a problem, use the Resolution Percentage slider, or convert to F4V to PNG instead and place that.
Not on this page. The density is fixed at 72 pixels per inch, which makes one pixel one PostScript point and gives a bounding box numerically equal to the pixel dimensions. Everything downstream scales from there: place the EPS at half size in your layout and it prints at 144 dpi, at a quarter size and it prints at 288 dpi. If you need a specific physical size, set it when you place the file rather than expecting the converter to do it.
One EPS per sampled frame, all at the same dimensions. Be deliberate with the Capture Rate, because these files are large and there is no cap on the count: a five-minute video sampled once per second is 300 files, and at 1080p that is nearly 3.8 GB of output. Start at one frame every 5 or 10 seconds, look at what you get, and tighten from there.
Adobe Illustrator, InDesign and any PostScript-aware print workflow read it directly, as do Ghostscript, Inkscape and the preview tooling on macOS. Photoshop can open it, though it rasterises on import — which is a no-op here since the content is already a raster. What generally cannot open it is a web browser or an image viewer that expects a bitmap format, because EPS is a program to be interpreted rather than a picture to be decoded.
It is one right way, and the only one if your workflow accepts EPS and nothing else. If the layout application will take a raster format, a PNG or a TIFF is a far better choice: same pixels, a fraction of the size, and no PostScript interpreter in the path. Reach for EPS when a printer, a template or an old publishing pipeline has specifically asked for it — F4V to JPG covers the common case where any image file will do.
The colour, yes — the frame is extracted as a lossless PNG before being written into the EPS, so nothing is lost between decode and embed. The aspect ratio is a subtler question: the bounding box is built from the frame's pixel dimensions, so if your source stores non-square pixels the EPS will display them as square and the picture will look horizontally stretched or squashed. F4V material is normally square-pixel H.264, so this rarely bites, but it is worth checking on anything transcoded from standard-definition sources.
No. The file declares %%Pages: 1 and the converter explicitly selects frame zero of whatever it is handed, so a single EPS always holds a single picture. "Multiple Screenshots" gets you multiple files rather than a multi-page document. If you need a single document containing several frames, assemble the individual EPS files into a PDF in a layout application.