Initializing... drag & drop files here
Supports: PS
PostScript (.ps) is a page-description language Adobe built for printing — vector paths and text the printer interprets into a page. Most browsers and image apps can't display a .ps file at all, and recent macOS releases dropped native support entirely. Rasterizing it to WebP turns those instructions into a single pixel image that opens anywhere and stays small: Google's format is roughly 26% smaller than PNG losslessly and 25–34% smaller than JPEG at matching quality. The trade-off is that vector lines and text become pixels and are no longer selectable or infinitely scalable — pick a DPI that matches how you'll use the result.
| Setting | What it does | Pick when |
|---|---|---|
| 72–96 DPI | Screen-resolution raster, smallest file | Web preview, email, thumbnails |
| 300 DPI | Print-grade detail, balanced size | Sharing a print-ready proof |
| 600–1200 DPI | Maximum detail, large file | Archival or fine-art scans |
| Lossless: No (Very High) | Lossy WebP, smallest size | Photos, gradients, most uses |
| Lossless: Yes | Pixel-exact, larger file | Line art, text, flat color |
| Image Transparency | Keeps an alpha channel | Logos and art over any background |
No. WebP is a raster (pixel) format, so converting flattens the vector paths and text into a fixed grid of pixels. You can't select the text or rescale the artwork without quality loss afterward. If you need the page to stay editable and resolution-independent, convert it to a document instead with PS to PDF, which preserves the original vectors and selectable text.
DPI sets how many pixels are rendered per inch of the original page, so it controls both sharpness and file size. For on-screen use, 72–96 DPI keeps the file small. For print-quality output choose 300 DPI, and for archival or fine-art detail go to 600 or 1200 DPI. Because a vector page has no inherent pixel resolution, picking a higher DPI is the only way to capture fine line detail — but it multiplies the pixel count and the file size.
WebP supports both. Lossy (Lossless set to "No") with a high quality preset gives the smallest files and is fine for photographic or shaded content. Lossless ("Yes") reproduces every pixel exactly, which matters for the crisp edges of line art, diagrams, and text typical of PostScript pages — at a larger file size. Google measures lossless WebP at about 26% smaller than an equivalent PNG, and lossy WebP at 25–34% smaller than a comparable JPEG.
It can. WebP supports an alpha channel in both its lossy and lossless modes, so enabling Image Transparency lets areas with no content stay see-through instead of filling with a background color. If you'd rather have a solid background — useful for documents or printing — set the Color option to White (or another color) and the page renders onto that fill.
A .ps file can describe several pages. Each page is rendered to its own WebP image at the DPI you choose, so a three-page PostScript document produces three WebP files in the download. There's no single WebP that stacks pages, because WebP is a single-image format rather than a paged document like PDF.
Apple removed native PostScript handling in stages: macOS Monterey and earlier could view and convert .ps and .eps files in Preview, Ventura dropped that from the Preview app, and Sonoma removed the underlying system rendering engine entirely. On those systems a .ps file no longer opens by double-clicking. xconvert renders PostScript with Ghostscript on our servers, so converting it to a WebP gives you an image that opens in any modern browser — Chrome 32+, Firefox 65+, Edge 18+, and Safari 16+ on macOS (14+ on iOS) — without installing anything. In our testing, a single-page A4 PostScript file rendered at 300 DPI lands around 200–500 KB as lossy WebP, depending on how much ink is on the page.