How to import Sketch files into Figma without breaking your design system

Quick answer

Figma opens .sketch files directly (File → Import, or drag the file onto the canvas). Symbols become components, shared text styles and color styles usually map across, but Sketch-only plugins, complex masks, and macOS fonts are where migrations stall. Import into a sandbox file, run a cleanup pass (rename, detach junk, rebind variables), then merge only what passes your checklist—do not treat the first import as production-ready. If you are still choosing a tool, read Figma vs Sketch (2026) for the strategic picture; for vector art from Adobe instead of Sketch, use Illustrator SVG cleanup.

Who this is for

• Teams leaving Sketch for multiplayer, Dev Mode, or cross-platform access.
• Agencies receiving client .sketch deliverables they must continue in Figma.
• Designers consolidating legacy libraries into a single Figma workspace.

---

Before you import: decisions that save days

Decision	Why it matters
One sandbox file per legacy Sketch library	Keeps broken imports off production pages
Font mapping table	Sketch PostScript names ≠ Figma family names on Windows
Symbol → component naming convention	Button/Primary beats Symbol 12 after import
Plugin replacement list	Sketch Runner, Craft, etc. need Figma equivalents
Cutover date	Stop editing Sketch the day you merge to Figma main

Document the cutover on your file cover page using how to organize a Figma file so future contributors know Sketch is archival only.

---

Method 1: Import the .sketch file (recommended)

Steps

1. In Figma, choose File → Import (or drag project.sketch onto the app).
2. Wait for conversion—large files with hundreds of symbols can take several minutes.
3. Open the imported file; pages usually mirror Sketch pages and artboards as frames.
4. Move everything to a page named 000 — Sketch import (do not ship) until cleanup finishes.

What converts well

• Artboards → top-level frames (verify dimensions).
• Symbols → components (often with variant-like structure if you used symbol overrides).
• Text styles and layer styles → Figma text/color styles (spot-check weights).
• Boolean operations and basic masks → usually intact.

What converts poorly

Sketch feature	Typical Figma outcome	Fix
Sketch-only plugin data	Missing or flattened	Rebuild affected layers
Complex symbol nests	Deep component trees	Flatten or rebuild variants
Bitmap filters	Rasterized or dropped	Reapply effects manually
Old gradient fills	Approximate colors	Rebind to variables
Layout grids (old)	May need recreation	Reapply layout grids on frames

Verdict: treat import as 80% structure, 20% polish—budget time for polish.

---

Method 2: Copy artboards via Sketch (when .sketch fails)

If a file is corrupt or uses a bleeding-edge Sketch beta:

1. Open in Sketch on macOS.
2. Select artboards → Copy.
3. Paste into a Figma sandbox frame.

Use this for one-off screens, not whole design systems—clipboard transfer drops metadata and symbol links.

---

Map Sketch symbols to Figma components

Rename immediately

Sketch symbol names often include slashes (Forms/Input/Default). Keep that pattern—it matches Figma component naming and helps Dev Mode handoff.

Audit overrides

Sketch symbol overrides become component properties or nested instances. Walk through:

• Text overrides → confirm font family exists on all platforms.
• Fill overrides → map to variables (variables & modes).
• Nested symbols → collapse duplicate components that imported as separate roots.

When to rebuild instead of import

Rebuild in Figma when:

• The symbol set predates auto layout and relies on absolute positioning.
• You need variant properties (size × state × theme) but imported as dozens of near-duplicate components.
• Accessibility or token governance requires a clean variable foundation (dark mode tokens).

---

Fonts, colors, and text styles

Fonts

Sketch files created on Mac often reference SF Pro or custom desktop fonts. On Windows or browser-only Figma:

• Install missing fonts locally, or
• Bulk-replace with your approved stack via Edit → Find and replace (font family).

Missing font warnings on import are normal—fix before publishing the library.

Color styles → variables

If your Sketch library used document colors, map them to Figma variables with modes instead of leaving hundreds of detached fills. This pays off the first time brand updates primary/500.

Text styles

Compare line height and letter spacing on body styles—Sketch defaults sometimes differ from Figma’s type panel by a pixel or two. Snap critical styles to your type ramp doc.

---

Plugins and features Sketch had that Figma handles differently

Sketch habit	Figma equivalent
Craft / data plugins	Content Reel, plugins, or real CMS data in prototypes
Anima / overflow scrolling	Prototype scroll settings + auto layout
Abstract versioning	Figma branching + multiplayer etiquette
Mirror preview	Figma mobile app / browser present
Measure redlines	Dev Mode + handoff plugins

Do not expect 1:1 plugin parity—list the three Sketch plugins your team actually used and find Figma replacements on the plugins pillar before cutover day.

---

Post-import cleanup checklist

Work on a dedicated page before merging into Design system / Components:

• Delete empty groups and 0% opacity layers left from conversion.
• Resize frames to your current device presets (mobile UI frames).
• Convert repeated patterns to auto layout (Auto Layout in practice).
• Replace absolute icons with library components from icon sets guide.
• Set export settings on components that ship assets (production export guide).
• Run a present/prototype pass on critical flows (create a prototype).
• Verify 2× exports are not blurry (fix blurry exports).

Only after the checklist passes should you publish or merge branch into the team library.

---

Team migration workflow (one week pattern)

Day	Focus
1	Import sandbox, inventory symbols vs rebuild list
2	Font + color token mapping
3	Component rebuild sprint (high-traffic UI only)
4	Page templates + layout grids
5	Dev pairing: Dev Mode + inspect on top components
6	Pilot squad ships one feature end-to-end
7	Archive Sketch repo read-only; announce in Slack

Link engineers to best Figma plugins for developers so inspect habits match the new file structure.

---

Common mistakes

Importing straight into the production library file
One bad mask pollutes every instance—sandbox first.

Keeping duplicate components (Button vs Button Copy vs Button/Primary)
Merge aggressively; variant properties beat three roots.

Ignoring Windows font gaps
Designers on PC see substitution cascades—fix fonts before critique.

Preserving Sketch’s absolute layout for responsive screens
Rebuild key templates with auto layout and constraints (see responsive design in Figma).

Assuming plugins migrated
Re-audit accessibility (accessibility plugins) and content tools manually.

---

Troubleshooting

Import fails or hangs.
Update Figma desktop; try splitting the Sketch file into smaller pages in Sketch first.

Symbols became flat groups.
The source may have been detached in Sketch already—rebuild as components.

Blurry images after import.
Re-link @2× assets; check export dimensions.

Gradients look banded.
Rebuild with Figma gradients or variables; old Sketch mesh gradients may rasterize.

Prototype links missing.
Sketch prototyping does not map 1:1—rewire in Figma using animation patterns.

---

FAQ

Can I edit .sketch in Figma and sync back to Sketch?

No—Figma import is one-way. Keep the .sketch archive for reference only.

Do I need a Mac to import?

.sketch import works on Figma desktop and browser; you only need Mac + Sketch for the clipboard workaround or pre-export fixes.

Will my Sketch Cloud libraries auto-migrate?

No—export local copies or request .sketch files from library owners.

How does this relate to Figma vs Sketch commercially?

Import solves delivery; Figma vs Sketch solves whether to switch. Do not conflate the two decisions.

Should illustrators still use Sketch?

If they export assets only, see Illustrator import—product UI should still live in Figma after cutover.

---

Next steps

Import one representative Sketch file today, run the cleanup checklist, and list ten components to rebuild vs keep. Schedule a dev pairing session on the cleaned file before you merge into the team workspace. For broader tool strategy, visit the Figma guides hub and comparisons hub.