Microsoft Publisher to WebP converter
Microsoft Publisher pages are laid out by our office engine and rendered to WebP by our image engine, one image per page; publications with several pages download as a ZIP.
- Converted with Office engine → Image engine · input deleted within 24 h
- Free: 5 conversions a day · 5 MB each
- Higher limits →
What changes
- Microsoft Publisher pages are laid out by our office engine and rendered to WebP by our image engine, one image per page; publications with several pages download as a ZIP.
- EXIF, color profiles, layers, animation frames, and camera metadata may be stripped unless the destination requires minimal metadata.
- Transparency stays for PNG and WebP but is filled with the selected background for JPEG, BMP, PDF, and other opaque targets.
- Fonts missing on the server are substituted before rendering, so text can wrap differently from the original file.
- SVG input is rasterized at the requested dimensions or DPI, producing pixels rather than editable vector paths.
- Server-only codecs or PDF rendering are used when browsers cannot safely handle the pair.
A real Microsoft Publisher → WebP run
We converted our Microsoft Publisher sample (158 KB) with Office engine → Image engine on 2026-10-20. It took 2.5 s and produced a 339 KB WebP file, 2.1× larger than the input. The engine raised 4 warnings, listed below.
Input · sample.pub · 158 KB
OLE2 compound document (legacy Office binary)
Output · sample.zip · 339 KB
ZIP with 2 page images (sample-page-1.webp … sample-page-2.webp)
- Archive parts
- 2
- first
- sample-page-1.webp
- Fonts that are not installed on our servers are replaced with substitutes, so text can wrap differently from Publisher.
- Text that flows between linked frames can overrun its box on multi-column pages; check each page before printing.
- PDF pages rendered as images; selectable text is not preserved.
- 2 pages written as one WEBP each inside a ZIP.
Options
- width
- Set the output width in pixels.
- height
- Set the output height in pixels.
- fit
- Contain, cover, or fill within the requested dimensions.
- quality
- Set lossy output quality where the codec supports it.
- background
- Fill transparency with this color for opaque formats.
- stripMetadata
- Remove source metadata when writing the output.
- dpi
- Rasterize SVG or PDF-derived pixels at the requested scale where supported.
Example
Microsoft Publisher image, 1200 × 800 pixelsWebP image resized or re-encoded without OCR text extractionDo it in code
soffice --headless --convert-to pdf input.pub && pdftoppm -png -r 144 input.pdf slideMicrosoft Publisher to WebP by API or MCP
The HTTP API and the MCP server run the exact engine this page uses (Office engine → Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=pub&to=webp.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.pub" -F "from=pub" -F "to=webp" \
-F 'options={"width":0}' \
--output output.webpOptions this engine accepts for Microsoft Publisher → WebP
| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing WebP | number | 0 |
| height | Writing WebP | number | 0 |
| fit | Writing WebP | contain · cover · fill | contain |
| quality | Writing WebP | number | 90 |
| background | Writing WebP | string | #ffffff |
| stripMetadata | Writing WebP | boolean | true |
This converter works today; a tested write-up of what changes for Microsoft Publisher → WebP is in progress.