Skip to main content

Features That Don’t Translate from Figma to Email

Check out this article for FAQs about certain features in Figma and best practice recommendations for building for Knak emails!

Updated this week

🎨 Opacity & Blending Modes

  • Figma allows it. Email editors don’t.

  • Effects like faded overlays, ghost buttons, or transparent images won’t translate in emails.

  • Fix: Use solid colors or flatten transparent elements into images.

🧊 Drop Shadows and Inner Shadows

  • Box/text shadows are either unsupported or render inconsistently in email clients

  • Fix: Keep shadows subtle, or bake into image assets.

🖼️ SVGs or Vector Shapes

  • Fix: Export as PNG or JPG, especially for icons and logos.

📐 Auto Layout / Flex-Like Responsive Behavior

  • Knak is modular and use table-based layouts under the hood.

  • Stacking, spacing, and responsiveness don’t behave like web.

  • Fix: Design with clear row/column structure and avoid overlapping elements.

🔠 Custom Fonts

  • Ensure your custom font is brand approved and available in Knak

🧁 Gradients

  • Many email clients don’t render gradients well (especially in buttons/backgrounds).

  • Fix: Use solid background colors

🧩 Hover States or Interactions

  • No hover, no animations.

  • Fix: Design everything as static. Add interactions in Knak.

🧱 Complex Nesting or Grouping

  • Nested auto layout frames in Figma don’t translate into modular content blocks.

  • Fix: Build with the drag-and-drop structure in mind: rows > columns > content.

💎 Layering or Z-Index Design

  • Stacking elements (e.g., text over images) can’t be easily recreated.

  • Fix: Use image editing tools to flatten text + image if layering is essential.

✅ Pro Tips for Figma-to-Email Editor Workflow

  • Design in a 600px-wide frame to match the email editor.

  • Use a layouts that mirrors the Knak editor’s structure (e.g., 1-column, 2-column, etc.)

Did this answer your question?