Skip to main content
Moda supports several export formats. The default format depends on your canvas type: slide decks default to PPTX, document canvases default to PDF, animation canvases default to MP4, and other canvases default to PNG.

​
Available formats

​
Exporting as PDF

PDF export creates a hybrid PDF with:
  • Selectable text: Text elements are rendered as real text in the PDF, not rasterized
  • Vector elements where possible
  • Hyperlinks preserved from the design
There is also a Flatten PDF option that rasterizes everything, which can be useful if the hybrid PDF has rendering differences.

​
Exporting as PowerPoint (PPTX)

PowerPoint export converts your design to a native .pptx file:
  • Supported elements are converted to native PowerPoint objects (text, shapes, images)
  • Backgrounds are detected and placed as slide masters (non-editable background layer)
  • Unsupported shapes are rasterized — complex vector elements that don’t have a PowerPoint equivalent are rendered as images

​
What transfers as an editable object

These element types can leave Moda as native PowerPoint objects rather than pictures: Animations do not transfer to PowerPoint.

​
What gets flattened to an image, and why

Some effects have no PowerPoint equivalent. When an element uses one, that element exports as a picture instead. It’s per element, not per slide — one shadowed shape becomes a picture while the text and tables around it stay editable. For the element types in the table above, this is the complete set of styling reasons one of them turns into a picture: How to read the second column. An element type that isn’t listed on a row still exports as a real PowerPoint object when it has that effect. Lines and tables have no styling gate at all beyond clipping, and text adds only a distort warp. The tradeoff is that the effect itself may not survive: you get an editable line rather than a picture of one, but the styling PowerPoint can’t express is dropped or approximated rather than preserved. For the element types that do gate on an effect, the whole element rasterizes so the effect is kept. Three rows need a word of explanation:
  • image fill says Containers, not rectangles, on purpose. A plain rectangle with an image fill isn’t flattened — it leaves the shape lane and exports through the image lane, still a native picture. A container with an image fill has no such lane to move to, and neither does an ellipse.
  • non-solid fill priority is split for the same reason. On a rectangle the two priorities you actually produce — an image fill and a video fill — move to the image and video lanes instead of flattening, so only gradient and shader priorities rasterize it.
  • rotation beyond the embed tolerance means a video or chart rotated more than 0.5°.
Generated graphics — a chart or illustration saved as a single image asset — appear on one row only. They export as an embedded picture and are flattened just by clipping, so a generated graphic keeps its shadow, blur, or blend mode and still lands as a native picture.

​
Other reasons something can still export as a picture

The table above covers styling. Two things sit outside it:
  • Charts drawn as live shapes. A bar, line, area, pie, or doughnut chart Moda renders as its own bars, axes, and labels becomes a real PowerPoint chart you can restyle and edit the data of; PowerPoint lays it out itself, so it is editable rather than pixel-identical. Any other chart type always exports as one picture of the whole chart, and the Charts rows above say which of the supported ones still flatten. A chart saved as a single image asset is the case above and behaves differently.
  • Images whose source can’t be read at export time. If the image bytes can’t be fetched, or an SVG has no intrinsic size to render at, that image stays in the picture layer even though nothing in the table applies to it.

​
Video: when an embed becomes a still

A video that clears everything above can still fall back to its poster frame. The usual reasons show up only while the file is being written:
  • the media type isn’t one PowerPoint can embed
  • the clip is over the per-video size cap, or the export has already used its total embedded-video budget
  • fetching the file failed
  • PowerPoint rejected the media while the slide was being written
In each case the export falls back to the clip’s poster image in the same spot. A clip with no usable poster leaves a gap there instead.
The table above is checked against the exporter’s own rules in CI: the causes and the element types each one applies to are read out of the export code. If you hit a case that doesn’t match what you see here, that’s a bug worth reporting rather than expected variance.

​
Exporting as PNG / JPG

Raster image export renders your design as a pixel image:
  • You can choose the export scale (1x, 2x, 3x, etc.) for higher resolution
  • You can export individual pages or all pages
  • Very large exports (dimensions over 8,192px or area over 50 million pixels) use tiled rendering to work within GPU limits
  • If rendering fails at high scale, Moda automatically retries at 1x scale

​
Exporting as video

Video export is available for designs with animations:
  • MP4 (single page): Exports one page’s animation as an H.264 (or H.265) video — frame rate selectable: 24, 30 (default), or 60 FPS
  • GIF (single page): Exports one page’s animation as a GIF — frame rate selectable: 10, 12 (default), 15, or 24 FPS
  • WebP (single page): Exports one page’s animation as an animated WebP at 15 FPS — smaller than GIF and supports transparency
  • MP4 Full Video (all pages / Main Edit): Exports all pages as a single video with transitions between slides, or the canvas’s Main Edit timeline. The in-app dialog renders these at 30 FPS; the API and CLI accept 24, 30, or 60
Video exports render and encode server-side on Moda’s native render lane. The per-file budget is per format: MP4 allows 18,000 frames and 600 seconds, GIF and WebP allow 9,000 frames and 300 seconds — whichever binds first. At 60 FPS the frame budget caps an MP4 at 300 seconds. Large exports may take longer and continue in the background; you’ll get the file when they finish. For mixed page sizes in full video export, Moda adds letterboxing to maintain consistent dimensions.

​
Exporting for Google Slides

Google Slides export is available for slide and document canvases (the export dialog offers it only for slides and documents):
  1. Connect your Google account from the export menu
  2. Click Export to Google Slides
  3. The exported presentation opens in a new tab in Google Slides

​
What transfers and what doesn’t

  • Text, basic shapes, and many images transfer as editable Google Slides content
  • Complex vector artwork, blends, SVG-backed assets, and advanced image treatments may be rasterized for fidelity
  • Semi-transparent text may appear more opaque after export because Slides does not preserve editable text alpha reliably
  • Custom letter-spacing does not transfer
  • Animations do not transfer
  • Portrait and custom page sizes may still open as standard 16:9 Slides presentations
Google Slides export is a best-effort conversion. Moda keeps content editable where the Slides API supports it and uses raster fallbacks where fidelity matters more than editability.

​
Downloading individual slides vs. full deck

When exporting, the page selector at the top of the export dialog offers:
  • All pages — every page in the design
  • Current page — just the page you’re on, named so you can confirm it’s the right one
  • Selected pages — tick individual pages from the list
For formats that produce one file per page (PNG, JPG), exporting several pages gives you a ZIP. PDF and PPTX combine the selected pages into a single document.