Infographic deck as JPEGs
- Input
- 382,621-byte Keynote 8.3 deck with six 16:9 slides on a dark grey background.
- Output
- 866,490-byte ZIP with six 3840 × 2160 JPEGs; layout took 7.8 s and rendering 7.9 s.
Keynote → JPG gives a picture of each slide in the format every learning platform and social site accepts, and photo-heavy decks shrink well as JPEG.
From real runs
| Element | Result | What happens |
|---|---|---|
| Slide images | Kept | A six-slide infographic deck produced six JPEGs, zipped together in slide order. |
| File size | Changed | The five-slide photo-book deck was a 145,307-byte ZIP as JPEG against 787,131 bytes as PNG, because its flat backgrounds compress well. |
| Pixel size | Changed | 16:9 slides render at 3840 × 2160 by default; width 1280 gave 1280 × 720 images for a three-slide deck. |
| Presenter notes | Lost | Notes belong to the deck, not the slide picture, so none of them appear in the JPEGs. |
| Slide appearance | Changed | Images inherit the office layout, including black colour bands on the light-bulb infographic and a title that wraps into its subtitle. |
| Transparency | Lost | JPEG cannot hold transparent areas; every slide has its solid background or white. |
A six-slide infographic deck produced six JPEGs, zipped together in slide order.
The five-slide photo-book deck was a 145,307-byte ZIP as JPEG against 787,131 bytes as PNG, because its flat backgrounds compress well.
16:9 slides render at 3840 × 2160 by default; width 1280 gave 1280 × 720 images for a three-slide deck.
Notes belong to the deck, not the slide picture, so none of them appear in the JPEGs.
Images inherit the office layout, including black colour bands on the light-bulb infographic and a title that wraps into its subtitle.
JPEG cannot hold transparent areas; every slide has its solid background or white.
We converted our Apple Keynote sample (268 KB) with Office engine → Image engine on 2026-10-20. It took 1.6 s and produced a 149 KB JPEG file, 44% smaller than the input. The engine raised 3 warnings, listed below.
Input · sample.key · 268 KB
ZIP with 62 parts
Output · sample.zip · 149 KB
ZIP with 3 page images (sample-page-1.jpg … sample-page-3.jpg)
LibreOffice and pdftoppm
soffice --headless --convert-to pdf deck.key && pdftoppm -jpeg -jpegopt quality=85 -scale-to-x 1280 -scale-to-y -1 deck.pdf slideSame import and the same theme caveats as the PDF route.
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=key&to=jpg.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.key" -F "from=key" -F "to=jpg" \
-F 'options={"width":0}' \
--output output.jpg| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing JPEG | number | 0 |
| height | Writing JPEG | number | 0 |
| fit | Writing JPEG | contain · cover · fill | contain |
| quality | Writing JPEG | number | 90 |
| background | Writing JPEG | string | #ffffff |
| stripMetadata | Writing JPEG | boolean | true |
Most platforms display slides at 1280 or 1920 pixels wide. Set width to that value; the default 3840-pixel images are larger than needed and slower to upload.
That deck draws the bulb with layered colour fills our office engine did not reproduce, and the image shows the slide as it was laid out. Check theme-heavy slides in the preview before sharing.
Yes. One slide gives one JPG; several slides give a ZIP with one JPG per slide in order. Build steps are not split into separate images.