MODO
LEARN MODO / PRACTICAL GUIDE

Exchange designs with Figma

Experimental integration · setup requiredReviewed 2026-10-20
A guide to the current beta, not a release announcement.

These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.

MODO Design Bridge exchanges a supported design subset using .modo-figma.json. It does not open or write Figma's native .fig format.

Install the bridge

  1. Choose File → Figma: import and export… to open Figma design exchange.
  2. Choose Download Figma plugin and unzip the package.
  3. In Figma desktop, choose Plugins → Development → Import plugin from manifest.
  4. Select the package's manifest.json and run MODO Design Bridge.

This is a development-plugin installation, not a claim that the plugin is published in Figma Community. The bridge itself does not require a Figma API token or remote network service. Access to Figma and its files follows Figma's own requirements.

Bring a Figma design into MODO

  1. Select the intended frames in Figma.
  2. Use Export selection in the bridge.
  3. In MODO, select that .modo-figma.json as the Figma exchange file.
  4. Review the indicative preview, new-page count and Conversion report.
  5. Acknowledge the adaptations and choose Import as new pages.
  6. Inspect the imported text, layout, vectors and images. Use Undo if the result is not what you intended.

Existing pages are not replaced. If the document changes while a plan is open, prepare a fresh import.

Send a MODO design to Figma

Choose Current page or Whole project, then Export design for Figma. Review and save the conversion report. Import the exchange through MODO Design Bridge in your destination Figma file.

Know the boundary

The exchange covers supported pages, frames, stack layout, plain text, images, vectors, components, instances and color tokens. It uses the Primary design and one project theme.

Responsive overrides, CMS behavior, native app logic and Motion timelines are not transferred as equivalent Figma features. Customized instances may become editable frames. Missing fonts require an explicit fallback; font binaries are not carried with this exchange. Animated GIF/WebP images become static images with a reported adaptation.

Keep the original MODO .modo and original Figma file. A round trip is not a lossless backup, and a conversion report is part of the deliverable.

Shared with the app’s offline Help · 0.1.0-alpha.1-docs.2
Need a correction? Tell us