Skip to content

Import and Export

MikroSlides uses explicit files for handoff and backup. Browser storage is convenient for daily work, but important decks should also be exported.

You can export:

  • JSON as editable .mikroslides.json deck data
  • Portable .mikroslides files with editable deck data plus embedded image and font assets where available
  • PDF through the browser print dialog
  • PNG for the current slide

Use JSON for compact editable backups. Use portable export when the deck contains local images or fonts and should travel as one file.

You can import:

  • .mikroslides.json deck files
  • portable .mikroslides files
  • Markdown deck sources: .md, .markdown, or .mikroslides.md

Imported decks are copied into local browser storage as new decks, so the source file remains an external backup.

Use Markdown when you want to draft a deck textually or generate a first version from another tool. Ordinary Markdown headings work, and MikroSlides Markdown adds optional frontmatter, slide separators, layout metadata, images, skipped-slide state, transitions, and speaker notes.

See File Formats for the Markdown authoring format and JSON schema.

Local image files are stored in the browser and can be embedded in portable exports. Remote image URLs are loaded by the browser when the deck renders. Portable and PNG export may fetch remote URLs already present in the deck so they can be embedded or rendered.

Local font files and selected remote font sources can be stored with the deck. Portable export includes local font assets where available.

For important decks, export a JSON or portable file and keep it with the project it supports. Browser storage is local to the current browser profile and origin.