Convert EPS to WebP
An EPS is a PostScript program from an era when the destination was a printing press. A WebP is a codec built for a browser to download quickly. This conversion crosses about twenty-five years of assumptions in one step, and the interesting part is which of them survive.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your EPS file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Rendered at 150 dpi, not the default 72
- Transparency preserved where the drawing had it
- The smallest of the EPS conversions here
- Nothing to install
How to use EPS to WebP
- 1
Add the EPS
Drop it in. Ghostscript interprets the PostScript, which is what makes an EPS readable without any design software.
- 2
Rendered, then encoded
Rasterized at 150 dpi and encoded as WebP at quality 82, alpha channel carried through.
- 3
Put it on the page
Every browser since 2020 reads WebP. Keep a PNG fallback only if you support older ones.
How it works
Ghostscript interprets the PostScript at 150 dpi with its sandbox enabled, and the rendered image is encoded as WebP at quality 82 with any transparency carried through.
Twenty-five years in one step
The two formats were designed for opposite constraints, and it is worth seeing what each was optimizing for.
EPS, 1987. The destination is a printing press whose resolution is unknown and possibly enormous. So the file describes the drawing rather than the pixels: curves as control points, fills as instructions, text as glyphs and positions. Size on disk is nearly irrelevant; the machine reading it has time.
WebP, 2010. The destination is a browser on a phone on a mobile network. So the file is a grid of pixels compressed as aggressively as the eye will tolerate, with an alpha channel because web pages have backgrounds of their own. Fidelity is negotiable; bytes are not.
Converting between them is therefore not a translation but a decision: fix the resolution, accept a little loss, and get a file a browser can actually show. No browser has ever rendered EPS natively, so the alternative is not a worse image — it is no image.
Which EPS conversion to pick
| you want | use |
|---|---|
| it on a web page | this one |
| it on a web page, pixel-exact | /eps-to-png |
| it sent to a printer | /eps-to-pdf, which keeps the vectors |
| a form that only takes JPEG | /eps-to-jpg |
The one that loses nothing is /eps-to-pdf: PostScript and PDF are the same idea a generation apart, so the drawing is transcribed rather than photographed. Everything else here rasterizes, and the only question is how much you compress afterwards.
What to keep
The EPS. It is the only version that still contains the geometry, and any of these conversions can be run again from it at any size. A WebP cannot produce a larger WebP, and enlarging it makes the compression artifacts larger along with everything else.
Check the folder before you convert
Worth thirty seconds, because it often makes the conversion unnecessary.
Brand packs and asset deliveries from the last fifteen years usually contain
several formats in parallel — an eps/ folder for print, a png/ folder for
screen, and increasingly an svg/ one. The EPS is the file you noticed because
it is the one that would not open; it may not be the file you want.
If there is an SVG, use it. It stays vector all the way into the browser, is sharp on every screen at every zoom, and for a logo is frequently smaller than this WebP would be. If there is a PNG at a sensible size, /png-to-webp gets you the same result without a rasterization step in between.
Convert the EPS when it is genuinely the only version you have — which, for anything older than about 2010, it often is.
Examples
An old logo going on a new site
The file the brand pack shipped in 2009 becomes one a browser downloads in a few kilobytes, background still transparent.
A diagram for documentation
Smaller than the PNG for the same picture, which matters on a page that carries thirty of them.
Frequently asked questions
What survives the conversion and what does not?
The picture survives; the scalability does not. An EPS is drawing instructions with no fixed resolution, so it can be printed at any size. A WebP is a grid of pixels at one size chosen at conversion time. What you gain is a file a browser downloads in kilobytes rather than one it cannot display at all — no browser has ever rendered EPS natively.
Why is the output bigger than the bounding box says?
Because the bounding box is in points and the output is in pixels. Points are 1/72 inch, and the near-universal 72 dpi default makes one point one pixel — which turns a 200 by 150 point drawing into a 200 by 150 image, a thumbnail of something meant for a page. Rendering at 150 dpi gives 417 by 313 from that same file, measured, which is a size you can actually use.
Is WebP the right choice for a logo?
It is a good one and SVG is usually better, because SVG stays vector into the browser and is sharp at any zoom on any screen. This site does not offer eps-to-svg: the conversion available here traces the rendered pixels with potrace and discards the real paths, which is a worse file dressed up as a feature. If you have Illustrator, Inkscape or CorelDRAW, opening the EPS and saving as SVG is the better route.
Can I send this to a printer?
No. WebP is lossy here, RGB only, and unreadable by essentially all print software. Printers want the vectors — /eps-to-pdf keeps them, producing a PDF that embeds no images at all and renders sharply at whatever size the press runs at. That is the conversion for a print handoff; this one is for a web page.
Does my file leave my computer?
Yes. PostScript is a programming language and interpreting it safely needs Ghostscript with its sandbox on, which is a server job rather than a browser one. Your file and the result are both deleted within 30 minutes by a timer, and nothing is stored, indexed or examined.