To export from Miro, open the board’s three-dots menu, select Board > Export, and choose the format that matches your goal. Use PDF for a framed visual document, JPG or SVG for an image, CSV for text extraction, or an .rtb backup for restoring the board inside Miro. These files preserve different information, so none should be treated as a complete substitute for the others.
Start by deciding what must survive: the board’s appearance, its text, or the ability to restore it in Miro. Export availability can vary by plan, device, browser, board settings, and content. Check Miro’s current board export guide before relying on a particular option.
For an important board, a practical preservation bundle may combine a visual export, a text export, a restoration archive, and separate evidence for comments or voting. The right bundle is the smallest set of artifacts that preserves the board’s actual business purpose.
How to export a Miro board: choose the format by what you need to keep
Use this table to choose an export based on the job it must do. An image, CSV file, backup, and diagram handoff are different artifacts with different limits.
| Need | Format | What it preserves or does not preserve |
|---|---|---|
| Share or print a framed visual record | Frames become pages in a multi-page PDF. Vector-quality PDF supports clickable links. Small file size PDFs do not support embedded links. | |
| Share a board area or frame as an image | JPG or SVG | Preserves visual output, not interactive editing. SVG is vector quality; JPG is a raster image. |
| Review or process text | CSV | Extracts supported text content but does not preserve general board layout or relationships. Tables retain their table structure. |
| Restore the board inside Miro | .rtb | A Miro restoration archive, not a portable file for another whiteboard product. |
| Hand off a Miro Diagram for Visio editing | VSDX | Available for Miro Diagrams on Enterprise plans, not a general export for arbitrary boards. Review the result in Visio. |
Choose an export by the information you need to preserve: layout, text, or the ability to restore the board in Miro.
Miro does not currently list PNG or PowerPoint as board-export formats. Its separate VSDX export for Miro Diagrams is limited to Enterprise plans and specific diagram content. It is not a general-purpose board conversion.
Check permissions, plan, device, and board structure first
Before exporting, confirm the account plan, device, board role, desired format, and board copying or export settings. A missing menu option may be a permission or compatibility issue rather than a problem with the board. If you cannot change the setting, ask the board owner or Miro administrator to check it. See Miro’s guide to copying and export permissions.
Free teams can have up to three active boards, and manual board backup is not included on the Free plan. Additional boards may remain view-only or locked. This does not mean that only three boards can exist, and access rights differ between team members, guests, visitors, and collaborators.
Use a supported browser or the desktop app for board export. Miro states that board export is not supported on mobile. Its current compatibility guidance also lists CSV as unsupported on mobile, tablets, Opera, and Edge versions below 79. Compatibility and plan behavior can change, so verify the current help page when troubleshooting.
For a multi-page PDF, create frames and review their order in the board overview panel. Each frame becomes a page. If a frame title must appear in the document, add it as a text widget because frame titles alone do not appear in ordinary exports.
Export a Miro board as JPG, SVG, or PDF
For a board-area image, open Board > Export > Save as image, select the area, choose an available size or quality, and export. Miro offers JPG and vector-quality PDF or SVG output. Free users are limited to small export sizes and cannot get high-quality exports without a watermark. Confirm the options shown for the current account.
- One frame: Open the frame’s context menu and choose Export as image.
- The entire canvas as one image: Select all objects, create a frame around them, then export that frame.
- Several PDF pages: Create frames for the required pages, arrange them in the board overview panel, and choose Board > Export > Save as PDF. Each frame becomes one page. Select only the required frames when the whole board is unnecessary.
- One-page PDF: Put the desired content in one frame and export it at Vector quality where available. If the Free-plan workflow requires temporary frame changes, follow Miro’s current instructions and confirm that the board can be recovered before making changes.
If clickable links matter, use Vector-quality PDF. Miro specifically states that Small file size PDFs do not support embedded links. Open the downloaded file and test a representative link rather than relying on its visual appearance.
JPG, SVG, and PDF preserve visual output rather than an interactive board. Objects cannot be moved in the resulting image or document. Uploaded bitmap images may already have been compressed during upload, while native Miro objects retain their quality in export.
Export Miro content as CSV and understand the data grain
Use CSV when text is the payload you need. Miro documents export for sticky notes, tables, cards, text boxes, and shapes. Export selected content from its context menu, or export the whole board through Board > Export > Export to spreadsheet (CSV). The documented output includes text, card description or URL, and sticky-note or card tags.
CSV is not a spatial copy of a board. It does not preserve general board structure and relationships, such as object positions, connectors, mind-map hierarchy, or clusters. Tables retain their table structure. Treat the documented column order as current guidance, not as a guaranteed stable API schema.
A CSV row is extracted content, not a reconstruction of a note’s spatial or relational context. Preserve the original file, source board, selection, export time, and file hash separately. Do not infer hierarchy or connectors from a flat list.
Before importing or transforming a CSV, check line breaks, empty fields, URLs, tags, and text encoding. If rows may become tasks, apply an explicit rule and require human review. For example, only rows with an agreed action tag may become task candidates. AI can suggest a category or draft title, but it should not decide that an ambiguous note is a commitment or reconstruct board hierarchy.
The following is an illustrative receiving-system record, not a Miro CSV schema. Its grain is one proposed record for one imported CSV row:
{
"source_file_sha256": "calculated-file-hash",
"source_row_number": 12,
"source_board_url": "recorded-board-url",
"classification": "action_candidate",
"proposed_title": "Review onboarding checklist",
"review_status": "pending"
}The row number is assigned during ingestion, not asserted to be a Miro object ID. For repeat imports, a proposed artifact key should distinguish the board snapshot, export type, selection, quality, and file hash. Do not use only board ID and date, because multiple runs or formats can occur on the same day. If concurrent processes can write records, enforce uniqueness in the receiving database or use a transactional upsert. A read-then-insert check alone is not race-safe.
Keep Miro as the source of truth until a reviewer confirms the mapping, ownership, and destination records. A cross-tool workflow can be designed around manual CSV, PDF, or SVG exports, but the reviewed Miro documentation does not establish a universal export API, webhook, or native one-click migration.
Save a restorable Miro board backup
Choose an .rtb file when you need a board archive intended for restoration inside Miro. It is not a portable format for another whiteboard product. Miro documents manual backups for Starter, Business, Enterprise, and Education plans, subject to role permissions. The normal interface has a 1 GB download and upload limit; contact Miro Support for larger files. Follow Miro’s backup and restore instructions.
- Open the board and choose Board > Export > Download board backup.
- Save the .rtb file in approved storage and record the board name, team, exporting user, date, file size, and SHA-256 hash.
- To restore it, use Create New > Import > Import backup in an eligible paid team. Test a business-critical backup on a non-production board first.
Downloading a backup is separate from board history versions. Miro documents board history separately, with versions retained for 90 days on eligible plans. History is not an independently stored backup, so preserve an .rtb file when an external restoration artifact is required.
What exports leave out and how to check the result
Ordinary exports do not include comments. Frame titles do not appear unless recreated as text widgets, and voting results require separate screenshot capture. If discussion or voting is decision-critical, capture it before exporting. A visual file or CSV alone is not a complete decision record.
Losses depend on the format. PDF, JPG, and SVG provide visual output rather than interactivity. CSV extracts text without general spatial relationships. An .rtb file is intended for restoration inside Miro. VSDX is limited to Miro Diagrams on Enterprise plans and has its own fidelity limitations, including possible differences in fonts, connector labels, freehand drawings, embedded content, prototypes, and data tables. Review a VSDX file in Visio before treating it as an editable handoff.
Object-heavy frames can disrupt export, including missing text. That does not mean every large board will fail. If the result is incomplete, divide the board into smaller logical sections, export them separately, and compare each artifact with the source board.
- Open the downloaded file and confirm that it is readable and complete enough for its stated purpose.
- Compare expected frames or representative CSV rows with the board.
- Test required PDF links and note any missing text or disrupted objects.
- Capture comments or voting separately when they matter to the decision.
- Store the artifact in an access-controlled location and record authorization when the board contains sensitive or personal information.
Troubleshoot a missing or failed export
Diagnose the problem in this order:
- Permission: Ask the board owner or administrator to confirm copying and export settings.
- Plan and format: Check whether the requested format or quality is available to the account. Miro’s current guidance also states that board export is not supported in developer teams.
- Device and browser: Board export is not supported on mobile. Check current compatibility guidance for CSV, tablets, Opera, older Edge versions, and the desktop app.
- Download behavior: Check whether the browser is blocking the file download or a pop-up.
- Selection size: For missing text or disrupted output, export smaller frames or logical sections and inspect each file.
If the issue persists, send the board owner or Miro administrator the board link, requested format, device and browser, and the error or missing content. Use Miro’s current board export troubleshooting guide for account and compatibility guidance.
Build a practical preservation bundle for an important board
When one file would leave a material gap, create a small preservation bundle. This is an operational recommendation, not an official Miro package:
- Vector-quality PDF: visual layout and clickable links where available.
- CSV: searchable text for review or downstream processing.
- .rtb backup: in-Miro restoration when the plan, role, and file-size conditions are met.
- Separate evidence: screenshots or notes for decision-critical comments and voting results.
Keep one manifest record per exported artifact. A multi-page PDF is one artifact, while separately captured voting results are distinct evidence. Useful proposed fields include the board URL or identifier, board name, team, exporting user, export timestamp, selected frames, format, quality, file size, SHA-256 hash, and validation status. These are tracking recommendations, not a Miro-published schema.
For downstream task mapping, preserve the source board and frame context, use deterministic rules where possible, and require human approval for ambiguous notes. A database-enforced unique constraint or transactional upsert should protect against duplicate artifact registration when multiple processes can run concurrently.
If the board contains confidential, customer, personal, or regulated information, confirm authorization before export and use access-controlled storage with appropriate retention and deletion rules.
The right preservation bundle is the smallest set of files that preserves what the board’s users actually need: a visual reference, usable text, a restoration path, or evidence of a decision.