<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sandeep Virk</title>
    <description>The latest articles on DEV Community by Sandeep Virk (@sandeep_virk_31621a43cb7c).</description>
    <link>https://dev.to/sandeep_virk_31621a43cb7c</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4217769%2F8af3be3d-fd8e-48cf-9827-7f3c14e4844e.jpg</url>
      <title>DEV Community: Sandeep Virk</title>
      <link>https://dev.to/sandeep_virk_31621a43cb7c</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sandeep_virk_31621a43cb7c"/>
    <language>en</language>
    <item>
      <title>Design Tokens for AI: Extract a Website's Real Colours, Fonts, Shadows and Icons So an LLM Builds On Brand</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Fri, 20 Nov 2026 06:41:58 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/design-tokens-for-ai-extract-a-websites-real-colours-fonts-shadows-and-icons-so-an-llm-builds-1boo</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/design-tokens-for-ai-extract-a-websites-real-colours-fonts-shadows-and-icons-so-an-llm-builds-1boo</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/website-design-tokens-for-ai" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; LLMs drift off brand because nobody gave them the brand. Design tokens for AI fix that: a short, exact list of colours, gradients, type, radii, shadows and icons that the model must use. WebCapture to Figma's Copy for LLM hands over those real values from a live page. You condense them into a token file or a style section, then reuse it in every prompt to Claude or ChatGPT.&lt;/p&gt;

&lt;p&gt;Ask an AI for "a pricing card in our style" and you get a nice card in someone else's style. The blue is a little off. The radius is 12 instead of 8. The font is Inter because Inter is safe. None of it is wrong, it just is not yours.&lt;/p&gt;

&lt;p&gt;The fix is not a longer adjective list. It is data. This post shows how to get the real style data from a site you own, how to shape it into tokens, and how to put it in a prompt so the model follows it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What design tokens are, in one paragraph
&lt;/h2&gt;

&lt;p&gt;Design tokens are named values for design decisions. &lt;code&gt;color.brand.primary&lt;/code&gt; instead of &lt;code&gt;#2160ff&lt;/code&gt;. &lt;code&gt;radius.card&lt;/code&gt; instead of &lt;code&gt;8px&lt;/code&gt;. They live in a JSON file, in CSS custom properties, or in Figma variables. For people, tokens keep a system consistent. For an LLM, they do something extra: they turn "on brand" from a feeling into a list it can check against.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why screenshots and URLs are not enough
&lt;/h2&gt;

&lt;p&gt;A screenshot gives a model pixels. It has to estimate hex values from compressed colours, guess the font from letter shapes, and approximate shadows by eye. Gradients are the worst case: the model sees a blend, not the stops.&lt;/p&gt;

&lt;p&gt;A bare URL is often no better. The model may not be able to open it, and even when a tool fetches the HTML, the final style lives in computed CSS across many files.&lt;/p&gt;

&lt;p&gt;What you want is the page as the browser rendered it, with values already resolved. That is what a capture gives you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Copy for LLM hands over
&lt;/h2&gt;

&lt;p&gt;Open the page in Chrome and capture it with the &lt;a href="https://www.figma.com/community/plugin/1688943241214350584/webcapture-to-figma" rel="noopener noreferrer"&gt;WebCapture to Figma&lt;/a&gt; extension. Then press Copy for LLM. The text on your clipboard carries:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Layout.&lt;/strong&gt; The structure and boxes of the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Colours.&lt;/strong&gt; Including real gradient stops, not just a "blue to purple" description.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Borders and shadows.&lt;/strong&gt; The actual border and shadow values.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fonts.&lt;/strong&gt; The type used on the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Icons.&lt;/strong&gt; As inline SVG, so the model uses your icons rather than look-alikes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interactions.&lt;/strong&gt; Every interaction, plus any flow you recorded.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is far more than a style guide. It is a full description of one page. For tokens, you want to compress it into the reusable part.&lt;/p&gt;

&lt;p&gt;Capture or rebuild only designs you own or have permission to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turning the capture into design tokens for AI
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Option A: ask the model to extract them
&lt;/h3&gt;

&lt;p&gt;Paste the Copy for LLM text into Claude or ChatGPT with an extraction prompt:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"From the captured page below, extract design tokens. Output JSON with groups: color, gradient, font, fontSize, fontWeight, lineHeight, radius, shadow, border, spacing. Use semantic names (brand, surface, text, muted, accent). Only include values that appear in the capture. Do not invent values. After the JSON, list any value you were unsure how to name."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The "do not invent" line is important. Without it, a model may fill gaps in a scale with tidy numbers that never appeared on the page.&lt;/p&gt;

&lt;p&gt;A trimmed result might look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"color"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"brand"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#2160ff"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"text"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#24252b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"accent"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#c9f56a"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"surface"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#ffffff"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"gradient"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"hero"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"linear-gradient(135deg, #2160ff 0%, #7a5cff 100%)"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"font"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"body"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Inter, sans-serif"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"radius"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"card"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"8px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"pill"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"999px"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"shadow"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"card"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"0 8px 24px rgba(36, 37, 43, 0.08)"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Treat this as a draft. Check every value against the capture before you rely on it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option B: read them from the Figma import
&lt;/h3&gt;

&lt;p&gt;Import the same page with the plugin. You get editable frames where colours, gradients, shadows, borders, corner radii and type are real layer properties. Select a button and the inspector shows its fill, radius and effect values.&lt;/p&gt;

&lt;p&gt;This route is slower but very reliable, and it is the natural path if you want Figma variables. Create the variables by hand from what you see, then bind them to the imported layers. For a fuller audit approach, see our guide to a &lt;a href="https://crafttor.com/blog/design-system-audit-from-screenshots" rel="noopener noreferrer"&gt;design system audit from screenshots&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option C: keep icons as a separate pack
&lt;/h3&gt;

&lt;p&gt;Tokens cover values. Icons are assets. Copy the inline SVG of each icon you want the model to reuse into a short "icons" block with a name per icon. Then you can say "use the &lt;code&gt;arrow-right&lt;/code&gt; icon" in later prompts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Writing the style section of a prompt
&lt;/h2&gt;

&lt;p&gt;Once you have tokens, wrap them in a fixed block you paste at the top of every UI prompt. Something like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;STYLE (must follow)
- Use only these tokens. If a value is missing, ask instead of inventing.
- Colours: brand #2160ff, text #24252b, accent #c9f56a, surface #ffffff
- Hero gradient: linear-gradient(135deg, #2160ff 0%, #7a5cff 100%)
- Font: Inter for all text. Weights 400, 600 only.
- Radius: 8px cards, 999px pills. Shadow on cards only: 0 8px 24px rgba(36,37,43,0.08)
- Icons: use the SVGs in the ICONS block. No icon fonts, no emoji.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then the task goes below: "Build a pricing section with three plans." Short, strict, reusable.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why a fixed block beats describing the brand
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;It is checkable. You can scan the output for any hex that is not on the list.&lt;/li&gt;
&lt;li&gt;It survives long chats. Paste it again when the model starts drifting.&lt;/li&gt;
&lt;li&gt;It is portable. The same block works in Claude, ChatGPT or a Figma code layer's AI.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Tokens as CSS custom properties
&lt;/h2&gt;

&lt;p&gt;If the model writes HTML and CSS, ask it to start from custom properties so every later change flows from one place:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;root&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nv"&gt;--color-brand&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#2160ff&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--color-text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#24252b&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--radius-card&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;8px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--shadow-card&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;8px&lt;/span&gt; &lt;span class="mi"&gt;24px&lt;/span&gt; &lt;span class="nf"&gt;rgba&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;37&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;43&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;0.08&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.card&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--radius-card&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;box-shadow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--shadow-card&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A rule in your prompt such as "never write a raw hex outside &lt;code&gt;:root&lt;/code&gt;" makes review much faster.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick review checklist
&lt;/h2&gt;

&lt;p&gt;After the model returns UI, run through this list:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;What to look for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Colour&lt;/td&gt;
&lt;td&gt;Any hex or rgb not in the token list&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gradient&lt;/td&gt;
&lt;td&gt;Stops and angle match the token&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Type&lt;/td&gt;
&lt;td&gt;Font family and weights match, no surprise fallback&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Radius&lt;/td&gt;
&lt;td&gt;Cards and buttons use the named radii&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shadow&lt;/td&gt;
&lt;td&gt;Shadows only where the tokens allow&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Icons&lt;/td&gt;
&lt;td&gt;Your SVGs, not generic substitutes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you only need a colour palette rather than a full token set, our post on &lt;a href="https://crafttor.com/blog/extract-colors-from-screenshot-figma" rel="noopener noreferrer"&gt;extracting colours from a screenshot in Figma&lt;/a&gt; is a lighter starting point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Privacy
&lt;/h2&gt;

&lt;p&gt;With the Chrome extension, captures pasted into the plugin stay on your machine. If you capture by URL instead, the URL is sent to Apify to be rendered using your own Apify token. Nothing from your Figma file is uploaded, and the plugin never sends anything to an AI. You paste the text yourself, so you choose what the model sees.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build your token block once, reuse it everywhere
&lt;/h2&gt;

&lt;p&gt;One careful capture of your homepage can give you a token file that keeps every later AI request on brand. Do it once, check every value, and keep the style block next to your prompts.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.figma.com/community/plugin/1688943241214350584/webcapture-to-figma" rel="noopener noreferrer"&gt;WebCapture to Figma&lt;/a&gt; is a free plugin. Capture a page you own and pull out its tokens today.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What are design tokens for AI?
&lt;/h3&gt;

&lt;p&gt;They are a compact, named list of your real style values that you give an LLM, so it builds UI with your colours, type, radii, shadows and icons instead of its defaults.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does WebCapture create Figma variables automatically?
&lt;/h3&gt;

&lt;p&gt;No. It imports real values onto editable layers and copies them as text with Copy for LLM. You create tokens or variables from those values.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will the model still invent values?
&lt;/h3&gt;

&lt;p&gt;Sometimes. Tell it to use only the listed tokens and to ask when one is missing, then check the output against your list.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I extract tokens from a page behind a login?
&lt;/h3&gt;

&lt;p&gt;Yes. Use the WebCapture Chrome extension, which captures the page as you see it. No Apify token is needed for that path.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does this work with ChatGPT as well as Claude?
&lt;/h3&gt;

&lt;p&gt;Yes. The token block is plain text, so it works in Claude, ChatGPT or a Figma code layer's AI.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>css</category>
      <category>design</category>
    </item>
    <item>
      <title>Figma Code Layer Animation: Make Captured Hovers, Transitions and Keyframes Play</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Thu, 19 Nov 2026 05:29:44 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/figma-code-layer-animation-make-captured-hovers-transitions-and-keyframes-play-am5</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/figma-code-layer-animation-make-captured-hovers-transitions-and-keyframes-play-am5</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/code-layer-hover-animations" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; A Figma frame can look exactly like a web page, but it cannot run the page's CSS. Hover states, transitions and keyframe animations need a browser engine. A Figma code layer animation runs that CSS for real. Capture the page with WebCapture to Figma, keep the frame for editing, and put the same page in a code layer when the motion has to play.&lt;/p&gt;

&lt;p&gt;You import a polished landing page into Figma. The layout, gradients and buttons are right. Then you press present and hover a button. Nothing happens.&lt;/p&gt;

&lt;p&gt;That is not a bug in your capture. It is the difference between a drawing of a page and a page that runs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a Figma frame cannot play CSS animation
&lt;/h2&gt;

&lt;p&gt;A Figma prototype has its own interaction model. You draw variants, connect them with triggers such as "while hovering" or "on click", and pick a Smart Animate or dissolve transition. It is a good system for designing new interactions.&lt;/p&gt;

&lt;p&gt;CSS works differently. A hover in CSS is a rule like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.card&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;200ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;box-shadow&lt;/span&gt; &lt;span class="mi"&gt;200ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.card&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateY&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;-4px&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;box-shadow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;12px&lt;/span&gt; &lt;span class="mi"&gt;24px&lt;/span&gt; &lt;span class="nf"&gt;rgba&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;0.12&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A keyframe animation is a named timeline the browser runs on its own:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@keyframes&lt;/span&gt; &lt;span class="nt"&gt;float&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="kt"&gt;%&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="kt"&gt;%&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateY&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="mi"&gt;50&lt;/span&gt;&lt;span class="kt"&gt;%&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateY&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;-8px&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.badge&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;animation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;float&lt;/span&gt; &lt;span class="mi"&gt;3s&lt;/span&gt; &lt;span class="n"&gt;ease-in-out&lt;/span&gt; &lt;span class="n"&gt;infinite&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Figma's prototype engine does not read selectors, pseudo classes or &lt;code&gt;@keyframes&lt;/code&gt;. So a Figma prototype cannot replay CSS animations, however faithful the frame looks. To rebuild them as prototype interactions, you would draw a variant for every state and wire each trigger by hand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where WebCapture puts the motion
&lt;/h2&gt;

&lt;p&gt;When you import a page with &lt;a href="https://www.figma.com/community/plugin/1688943241214350584/webcapture-to-figma" rel="noopener noreferrer"&gt;WebCapture to Figma&lt;/a&gt;, it detects hover states, transitions, CSS keyframe animations, scroll reveal effects and sticky or fixed positioning. It saves them with each layer as plugin data.&lt;/p&gt;

&lt;p&gt;So on the frame, the motion is recorded, not lost. The data travels with the layer. But a frame is still a frame. It shows the resting state, and the motion waits for something that can run it.&lt;/p&gt;

&lt;p&gt;That something is a code layer. As the plugin puts it: a frame looks like the page, a code layer runs it.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Behaviour&lt;/th&gt;
&lt;th&gt;On the imported frame&lt;/th&gt;
&lt;th&gt;In a code layer&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Layout, colours, type, icons&lt;/td&gt;
&lt;td&gt;Editable layers&lt;/td&gt;
&lt;td&gt;Rendered by real HTML and CSS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hover states&lt;/td&gt;
&lt;td&gt;Recorded as plugin data&lt;/td&gt;
&lt;td&gt;Play when you hover&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transitions&lt;/td&gt;
&lt;td&gt;Recorded as plugin data&lt;/td&gt;
&lt;td&gt;Play with their real timing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Keyframe animations&lt;/td&gt;
&lt;td&gt;Recorded as plugin data&lt;/td&gt;
&lt;td&gt;Loop as on the live site&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Links&lt;/td&gt;
&lt;td&gt;Prototype connections&lt;/td&gt;
&lt;td&gt;Work as links&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you want the full background on capturing the motion itself, read &lt;a href="https://crafttor.com/blog/hover-states-animations-to-figma" rel="noopener noreferrer"&gt;how to capture hover states and CSS animations from any website&lt;/a&gt;. This post is about the next step: making that motion play inside Figma.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two routes to a Figma code layer animation
&lt;/h2&gt;

&lt;p&gt;After an import, the plugin offers two ways to carry the page into a runnable form. Both keep your editable frame untouched.&lt;/p&gt;

&lt;h3&gt;
  
  
  Route 1: Download HTML
&lt;/h3&gt;

&lt;p&gt;Download HTML saves the page as a ready to run HTML, CSS and JS project. Its images and Google fonts are inside the project. Hover states, CSS animations and links work in it. If you recorded a flow with the Chrome extension, it replays too.&lt;/p&gt;

&lt;p&gt;Open it in a browser and you have a local, working copy of the motion to study and tweak.&lt;/p&gt;

&lt;h3&gt;
  
  
  Route 2: Copy prompt for Claude
&lt;/h3&gt;

&lt;p&gt;Copy prompt gives Claude, with the Figma MCP connected, everything it needs to add that project as a code layer beside your frame.&lt;/p&gt;

&lt;p&gt;There is a reason Claude does the last step. Figma plugins cannot create code layers themselves, because the Plugin API has no way to make one. So the plugin prepares everything, and Claude finishes the job through the MCP.&lt;/p&gt;

&lt;p&gt;Here is the flow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Import the page with WebCapture to Figma at the width you need.&lt;/li&gt;
&lt;li&gt;Run Copy prompt from the plugin after the import.&lt;/li&gt;
&lt;li&gt;Paste the prompt into Claude with the Figma MCP connected.&lt;/li&gt;
&lt;li&gt;Let Claude add the code layer next to your frame.&lt;/li&gt;
&lt;li&gt;Set the code layer to the size the prompt names. Code layers cannot be resized from the API, so you do this by hand.&lt;/li&gt;
&lt;li&gt;Press play and hover the elements that should move.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For a longer walkthrough of this route, see &lt;a href="https://crafttor.com/blog/website-to-figma-code-layer" rel="noopener noreferrer"&gt;turning a website into a runnable Figma code layer&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the motion once it plays
&lt;/h2&gt;

&lt;p&gt;Once the code layer is running, test it like you would test a staging build. A short checklist helps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hover every interactive element.&lt;/strong&gt; Buttons, cards, nav links and icons. Each one should change the way it does on the live site.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch the timing.&lt;/strong&gt; A 200ms ease out should feel quick and settled. If it feels sluggish, compare with the live page in a browser tab.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Let loops run.&lt;/strong&gt; Keyframe animations with &lt;code&gt;infinite&lt;/code&gt; should keep cycling without a visible jump at the loop point.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scroll the layer.&lt;/strong&gt; Scroll reveal effects and sticky headers depend on scrolling inside the layer, so scroll the whole page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click links.&lt;/strong&gt; They should still go where they went on the live page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare against the frame.&lt;/strong&gt; The resting state in the code layer should match the frame beside it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If something does not play, open the downloaded project in a desktop browser first. If it plays there, the issue is the layer size or setup. If it does not play there either, inspect the CSS. Our guide to &lt;a href="https://crafttor.com/blog/how-to-inspect-css-animations-in-chrome-devtools" rel="noopener noreferrer"&gt;inspecting CSS animations in Chrome DevTools&lt;/a&gt; shows how to slow an animation down and read its curve.&lt;/p&gt;

&lt;h2&gt;
  
  
  Editing the animation, not just viewing it
&lt;/h2&gt;

&lt;p&gt;A running code layer is not the end of the road. Because it is real code, you can change the motion directly.&lt;/p&gt;

&lt;p&gt;Common edits designers make:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Shorten a slow transition.&lt;/strong&gt; Change &lt;code&gt;transition: transform 400ms&lt;/code&gt; to &lt;code&gt;200ms&lt;/code&gt; for a snappier hover.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Swap the easing.&lt;/strong&gt; Try &lt;code&gt;cubic-bezier(0.2, 0.8, 0.2, 1)&lt;/code&gt; for a softer settle than plain &lt;code&gt;ease&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Respect reduced motion.&lt;/strong&gt; Wrap the decorative loops in a media query so users who ask for less motion get it:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@media&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nt"&gt;prefers-reduced-motion&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nt"&gt;reduce&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nc"&gt;.badge&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;animation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;none&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tone down the lift.&lt;/strong&gt; A &lt;code&gt;translateY(-4px)&lt;/code&gt; might become &lt;code&gt;-2px&lt;/code&gt; for a calmer product UI.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep your edits small and check each one by hovering in the layer. That way you always know which change caused what.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frame and code layer: use both
&lt;/h2&gt;

&lt;p&gt;You do not have to choose. Use the frame to edit copy, swap images, adjust spacing and hand off values. Use the code layer to show how the page feels and to test CSS motion edits without leaving Figma.&lt;/p&gt;

&lt;p&gt;One practical habit: name them clearly, for example "Pricing page / frame" and "Pricing page / code layer". Then nobody edits the frame expecting the motion to update.&lt;/p&gt;

&lt;p&gt;Capture or rebuild only designs you own or have permission to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Privacy and cost, briefly
&lt;/h2&gt;

&lt;p&gt;The URL you enter is rendered on Apify with your own API token, and a free Apify account is enough to start. Nothing from your Figma file is uploaded. For pages behind a login, use the Chrome extension, which needs no token. The plugin never sends anything to an AI, and it is free.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on a page with real motion
&lt;/h2&gt;

&lt;p&gt;Pick a page you own with a few hover effects and one looping animation. Import it, run Copy prompt, and put the code layer beside the frame. Then hover. The difference between "recorded" and "playing" is obvious within a few seconds.&lt;/p&gt;

&lt;p&gt;Get &lt;a href="https://www.figma.com/community/plugin/1688943241214350584/webcapture-to-figma" rel="noopener noreferrer"&gt;WebCapture to Figma on the Figma Community&lt;/a&gt; and make your captured motion play.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why do my imported hover states not work in Figma's prototype mode?
&lt;/h3&gt;

&lt;p&gt;A Figma prototype cannot replay CSS animations. WebCapture records hovers, transitions and keyframes as plugin data on each layer, but they only play in a code layer or in the downloaded HTML project.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can the WebCapture plugin create the code layer by itself?
&lt;/h3&gt;

&lt;p&gt;No. The Figma Plugin API has no way to create a code layer. The plugin prepares a prompt, and Claude with the Figma MCP connected adds the code layer for you.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why is my code layer the wrong size?
&lt;/h3&gt;

&lt;p&gt;Code layers cannot be resized from the API. Set the layer to the size named in the prompt, then press play.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do scroll reveals and sticky headers work too?
&lt;/h3&gt;

&lt;p&gt;WebCapture detects scroll reveal effects and sticky or fixed positioning and saves them with each layer. In a running code layer, scroll inside the layer to see them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is my Figma file sent anywhere?
&lt;/h3&gt;

&lt;p&gt;No. Nothing from your Figma file is uploaded. Only the URL you enter is sent to Apify to be rendered.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>css</category>
      <category>design</category>
    </item>
    <item>
      <title>Download Website as HTML: Get a Runnable Project From a Figma Capture</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Thu, 19 Nov 2026 05:29:09 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/download-website-as-html-get-a-runnable-project-from-a-figma-capture-3j8d</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/download-website-as-html-get-a-runnable-project-from-a-figma-capture-3j8d</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/download-website-html-project" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Most ways to download website as HTML give you a broken copy: missing fonts, dead hover states, images pointing back at the live server. WebCapture to Figma's &lt;strong&gt;Download HTML&lt;/strong&gt; saves a captured page as a ready-to-run HTML, CSS and JS project, with its images and Google fonts inside. Hover states, CSS animations and links work in it, and a flow recorded with the Chrome extension replays. You can open it in a browser, add it to Figma as a code layer, or use it as source material for an AI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why "Save page as" is not enough
&lt;/h2&gt;

&lt;p&gt;Every browser can save a page. Press Ctrl+S or Cmd+S, choose "Webpage, Complete", and you get an HTML file plus a folder of assets. It is a fair first try. In practice it often falls short:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fonts break.&lt;/strong&gt; Web fonts loaded from a CDN or via CSS may not come along, so text falls back to a system font.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Layout shifts.&lt;/strong&gt; Pages that build their layout with JavaScript can render differently, or not at all, when opened from disk.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assets point elsewhere.&lt;/strong&gt; Some images and styles still reference the live server. Offline, they are gone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;State is lost.&lt;/strong&gt; You get the page as it loaded, not after you opened a menu or switched a tab.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Command-line tools like &lt;code&gt;wget --mirror&lt;/code&gt; go further, but they copy a whole site's files, not one clean, self-contained page. You still have to sort out what is needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Download HTML gives you instead
&lt;/h2&gt;

&lt;p&gt;WebCapture works differently. It first captures the page into Figma as editable layers, recording how the browser laid it out. Then, after the import, &lt;strong&gt;Download HTML&lt;/strong&gt; saves that page as a project you can run.&lt;/p&gt;

&lt;p&gt;According to the plugin's documentation, the project:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;is plain HTML, CSS and JS, ready to run&lt;/li&gt;
&lt;li&gt;includes the page's images&lt;/li&gt;
&lt;li&gt;includes its Google fonts&lt;/li&gt;
&lt;li&gt;keeps hover states, CSS animations and links working&lt;/li&gt;
&lt;li&gt;replays a flow recorded with the Chrome extension&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because the images and Google fonts are inside the project, it does not depend on the original site to look right.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to download a website as HTML, step by step
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Capture the page
&lt;/h3&gt;

&lt;p&gt;Open WebCapture to Figma in a Figma file. You have two routes.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;By URL.&lt;/strong&gt; The page is rendered in a remote browser on Apify. Add your own Apify API token once; a free Apify account is enough to start.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;With the Chrome extension.&lt;/strong&gt; Best for pages behind a login or a bot wall. Capture the page as you see it and paste the result into the plugin. This route needs no token.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Choose a width before you import: Desktop 1440, iPad 820, Pixel 7, iPhone 14 Pro, iPhone SE, or a 360px Android phone. The width you pick is the layout you download. For more on picking breakpoints, read &lt;a href="https://crafttor.com/blog/mobile-and-tablet-website-to-figma" rel="noopener noreferrer"&gt;importing mobile and tablet websites to Figma&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Capture or rebuild only designs you own or have permission to use.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Optionally record a flow
&lt;/h3&gt;

&lt;p&gt;If you want more than the default view, record the clicks in the Chrome extension first, such as opening a menu or toggling a price. That flow replays in the downloaded project. The method is covered in &lt;a href="https://crafttor.com/blog/record-website-user-flow" rel="noopener noreferrer"&gt;recording a website user flow&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Press Download HTML
&lt;/h3&gt;

&lt;p&gt;After the import finishes, press &lt;strong&gt;Download HTML&lt;/strong&gt; in the plugin. Save the project into its own folder so its files stay together.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to open the project
&lt;/h2&gt;

&lt;p&gt;Open the folder and double-click the HTML file. It opens in your default browser. Hover the buttons, watch the animations, click the links.&lt;/p&gt;

&lt;p&gt;If anything does not load when opened straight from disk, serve the folder locally instead. Browsers apply stricter rules to &lt;code&gt;file://&lt;/code&gt; pages, and a local server avoids them. Two common options:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Python 3, from inside the project folder&lt;/span&gt;
python3 -m http.server 8000

&lt;span class="c"&gt;# Node.js&lt;/span&gt;
npx serve .
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then visit &lt;code&gt;http://localhost:8000&lt;/code&gt; (or the address &lt;code&gt;serve&lt;/code&gt; prints).&lt;/p&gt;

&lt;p&gt;Since it is a standard static project, you can also open it in your code editor, inspect the CSS, and change things.&lt;/p&gt;

&lt;h2&gt;
  
  
  What works, and what to expect
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;In the downloaded project&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Layout, colours, gradients, shadows&lt;/td&gt;
&lt;td&gt;Rendered as captured&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Images&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google fonts&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hover states&lt;/td&gt;
&lt;td&gt;Work&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CSS animations&lt;/td&gt;
&lt;td&gt;Play&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Links&lt;/td&gt;
&lt;td&gt;Work&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Recorded flow from the Chrome extension&lt;/td&gt;
&lt;td&gt;Replays&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A few practical notes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One page, one width.&lt;/strong&gt; The project reflects the page at the width you captured. Capture again at another width if you need a mobile version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Non-Google fonts.&lt;/strong&gt; The documentation mentions Google fonts being included. If a site uses a licensed font from elsewhere, check how it renders and swap it if needed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Server features do not come along.&lt;/strong&gt; Forms that post to a backend, search and logins depend on the original server. The project is a front end copy.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Three ways to use the project
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Open it as a reference
&lt;/h3&gt;

&lt;p&gt;Keep a dated snapshot of your own site before a redesign. Months later, you can still open it and see exactly how the old version behaved, including hover timing.&lt;/p&gt;

&lt;h3&gt;
  
  
  Add it to Figma as a code layer
&lt;/h3&gt;

&lt;p&gt;A frame can show hover states and animations only as recorded data, since a Figma prototype cannot replay CSS animations. A code layer runs them. Figma plugins cannot create code layers, because the Plugin API has no way to make one. So WebCapture offers &lt;strong&gt;Copy prompt&lt;/strong&gt;: paste it into Claude with the Figma MCP connected, and Claude adds the project as a code layer beside your frame. Set the layer to the size the prompt names, then press play. Code layers cannot be resized from the API, so this step is yours. The full walkthrough is in &lt;a href="https://crafttor.com/blog/website-to-figma-code-layer" rel="noopener noreferrer"&gt;turning a website into a Figma code layer&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Hand it to an LLM
&lt;/h3&gt;

&lt;p&gt;The project is real code, so it is useful context for an AI. You can attach the HTML and CSS files to a Claude or ChatGPT conversation and ask for a specific change. For example: "Convert this hero section into a React component, keeping the CSS values."&lt;/p&gt;

&lt;p&gt;If your goal is a fresh rebuild rather than an edit, the Chrome extension's &lt;strong&gt;Copy for LLM&lt;/strong&gt; is built for that. It carries the layout, colours with real gradient stops, border and shadow values, fonts, inline SVG icons, every interaction and any recorded flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Privacy
&lt;/h2&gt;

&lt;p&gt;With URL capture, the URL you enter is sent to Apify to be rendered. Nothing from your Figma file is uploaded. Captures pasted from the extension stay on your machine. The plugin never sends anything to an AI. If you share the project with Claude or ChatGPT, that is your choice and your paste.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get started
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.figma.com/community/plugin/1688943241214350584/webcapture-to-figma" rel="noopener noreferrer"&gt;WebCapture to Figma&lt;/a&gt; is a free plugin. Capture a page you own, press Download HTML, and open the result in your browser. You get an editable frame in Figma and a runnable project on disk from one capture.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How do I download a website as HTML with working fonts?
&lt;/h3&gt;

&lt;p&gt;Capture the page with WebCapture to Figma, then press Download HTML. The project includes the page's images and Google fonts, so it renders without reaching back to the original site for them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do hover states and animations work in the downloaded HTML?
&lt;/h3&gt;

&lt;p&gt;Yes. According to the plugin's documentation, hover states, CSS animations and links work, and a flow recorded with the Chrome extension replays.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I download a page that needs a login?
&lt;/h3&gt;

&lt;p&gt;Yes, through the Chrome extension. Capture the page as you see it, paste it into the plugin, then download. No Apify token is needed for this route.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Download HTML free?
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://www.figma.com/community/plugin/1688943241214350584/webcapture-to-figma" rel="noopener noreferrer"&gt;WebCapture to Figma&lt;/a&gt; is a free plugin. URL capture uses your own Apify account, and a free one is enough to start.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I edit the downloaded project?
&lt;/h3&gt;

&lt;p&gt;Yes. It is a standard HTML, CSS and JS project. Open it in any code editor, or hand it to an AI with a specific change request.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>css</category>
      <category>design</category>
    </item>
    <item>
      <title>image.to.design + Design Shapes: The Deadly Combination Every Figma Designer Needs</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Fri, 13 Nov 2026 11:18:34 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/imagetodesign-design-shapes-the-deadly-combination-every-figma-designer-needs-462i</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/imagetodesign-design-shapes-the-deadly-combination-every-figma-designer-needs-462i</guid>
      <description>&lt;p&gt;Most designers treat their Figma plugin stack as either/or. You pick a screenshot importer, or you pick a UI reconstructor. What almost no one realizes is that the two most talked-about tools in this space — image.to.design and Design Shapes — do completely different things. Used together, they cover the entire design pipeline with zero overlap.&lt;/p&gt;

&lt;p&gt;This is the combination that changes how fast you work.&lt;/p&gt;

&lt;h2&gt;
  
  
  What image.to.design actually does
&lt;/h2&gt;

&lt;p&gt;image.to.design by divRIOTS is a raw asset importer. You give it a URL, a screenshot, or a PDF, and it brings the visual content into Figma as-is — bitmap images, extracted colors, fonts where it can identify them. It is excellent at what it does: getting visual material off the web and into your canvas fast.&lt;/p&gt;

&lt;p&gt;What it does &lt;strong&gt;not&lt;/strong&gt; do is reconstruct the UI. The imported result is a flat image or a loose collection of elements. There are no auto-layout groups, no component structure, no SVG icons — just the pixels, organized roughly.&lt;/p&gt;

&lt;p&gt;That is not a criticism. That is by design. image.to.design is an asset pipeline tool, not a UI analysis tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Design Shapes actually does
&lt;/h2&gt;

&lt;p&gt;Design Shapes (by Crafttor) works from the other end. You give it a screenshot of a UI — a mobile app, a web page, a dashboard — and it uses AI to reconstruct the interface as editable Figma layers. It identifies interface elements, matches icons to Lucide SVG vectors, groups rows and columns with real auto-layout, and extracts the color palette as Figma Variables bound to every fill.&lt;/p&gt;

&lt;p&gt;The output is not a flat image. It is a working layer tree: named frames, text nodes, matched SVG icons, and design tokens — ready to edit.&lt;/p&gt;

&lt;p&gt;What Design Shapes does &lt;strong&gt;not&lt;/strong&gt; do is import arbitrary web content, PDFs, or raw brand assets. It is purpose-built for UI reconstruction, not asset harvesting.&lt;/p&gt;

&lt;h2&gt;
  
  
  The gap between them is exactly zero
&lt;/h2&gt;

&lt;p&gt;This is what makes the combination unusual: the tools do not compete. They do not even touch the same part of the workflow.&lt;/p&gt;

&lt;p&gt;image.to.design fills your canvas with raw material. Design Shapes turns UI screenshots into editable structure. One ends where the other begins.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four-step workflow
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Step 1 — Grab assets with image.to.design.&lt;/strong&gt; Paste the competitor's URL or drop in a PDF brand deck. Import logos, illustrations, and reference images straight into Figma as raw material.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2 — Screenshot the UI you want to reconstruct.&lt;/strong&gt; Capture the mobile app, landing page, or dashboard you need to work from — your own or a reference.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 3 — Run Design Shapes on the screenshot.&lt;/strong&gt; In one click, the flat screenshot becomes a structured layer tree with auto-layout groups, Lucide SVG icons, and color tokens extracted as Figma Variables.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 4 — Combine on canvas.&lt;/strong&gt; Drag your imported assets alongside the reconstructed UI. You have both: the raw brand material and the editable structure, in the same file.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who this workflow is built for
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Competitive analysis&lt;/strong&gt; — Import a competitor's site with image.to.design, then reconstruct their app UI with Design Shapes. You get their brand assets and their interface architecture in a single Figma file, fully editable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Client presentations&lt;/strong&gt; — Grab a client's existing PDF or web presence with image.to.design, reconstruct their current app UI with Design Shapes, and have a redesign-ready file inside an hour.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Design handoff&lt;/strong&gt; — Use image.to.design for marketing assets and illustrations, Design Shapes for the UI components that engineers will implement. Everything in one file, everything structured.&lt;/p&gt;

&lt;h2&gt;
  
  
  The credit math
&lt;/h2&gt;

&lt;p&gt;image.to.design has its own pricing. Design Shapes starts free — 5 credits when you sign up, plus a daily free credit that expires at midnight. Paid plans start at $9 for 60 credits.&lt;/p&gt;

&lt;p&gt;For most projects, the full four-step workflow above costs one Design Shapes credit. Neither tool charges you for the other's work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the free tier
&lt;/h2&gt;

&lt;p&gt;Design Shapes gives you enough free credits to run the full workflow on your first real project before you spend anything. Install it from the Figma plugin page, run it on a screenshot you already have, and see the layer tree it produces.&lt;/p&gt;

&lt;p&gt;Then stack it with image.to.design and you have the full pipeline.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>ux</category>
      <category>designsystem</category>
    </item>
    <item>
      <title>Toggle Switch Animation CSS: A Stretchy, Accessible Switch From a Checkbox</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Fri, 13 Nov 2026 04:37:59 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/toggle-switch-animation-css-a-stretchy-accessible-switch-from-a-checkbox-1g76</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/toggle-switch-animation-css-a-stretchy-accessible-switch-from-a-checkbox-1g76</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/toggle-switch-animation-css" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; A good toggle switch animation in CSS starts with a real checkbox, so it works with keyboards and screen readers for free. Slide the knob with &lt;code&gt;transform&lt;/code&gt;, fade the track colour, and add a short stretch to the knob while it moves. Finish with &lt;code&gt;role="switch"&lt;/code&gt;, a visible focus ring and a reduced-motion fallback. Or start from the Stretch Toggle in the Capture Motion gallery.&lt;/p&gt;

&lt;p&gt;Toggles look simple, but they are one of the most touched controls in any settings screen. A flat jump from left to right works. A knob that leans into the move and settles feels like a physical switch. The extra polish costs about ten lines of CSS.&lt;/p&gt;

&lt;h2&gt;
  
  
  The markup: a checkbox and a label
&lt;/h2&gt;

&lt;p&gt;Start with a native input. Do not build a toggle from a &lt;code&gt;div&lt;/code&gt; and JavaScript. You would have to rebuild focus, keyboard support and form submission by hand.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;label&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"switch"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;input&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"checkbox"&lt;/span&gt; &lt;span class="na"&gt;role&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"switch"&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"switch__input"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;span&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"switch__track"&lt;/span&gt; &lt;span class="na"&gt;aria-hidden&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"true"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;span&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"switch__knob"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/span&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/span&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;span&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"switch__label"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Email notifications&lt;span class="nt"&gt;&amp;lt;/span&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/label&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;role="switch"&lt;/code&gt; tells assistive tech this is an on and off switch, not a checkbox in a list. Screen readers then announce "on" or "off" instead of "checked". The visible track and knob are decoration, so they get &lt;code&gt;aria-hidden="true"&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Hide the input visually, but keep it in the page so it can take focus:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.switch__input&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;absolute&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;opacity&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;height&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Avoid &lt;code&gt;display: none&lt;/code&gt; here. It removes the input from the tab order and from the accessibility tree.&lt;/p&gt;

&lt;h2&gt;
  
  
  Toggle switch animation CSS: track and knob
&lt;/h2&gt;

&lt;p&gt;Now style the track and the knob. Use custom properties so sizes stay in sync.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.switch&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nv"&gt;--w&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;52px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--h&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;30px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--pad&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;calc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--h&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;-&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--pad&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;display&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;inline-flex&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;align-items&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;center&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;gap&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;12px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;cursor&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;pointer&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nc"&gt;.switch__track&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;relative&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--w&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;height&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--h&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;999px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#c9c9d1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;background-color&lt;/span&gt; &lt;span class="mi"&gt;220ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nc"&gt;.switch__knob&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;absolute&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;top&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--pad&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;left&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--pad&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;height&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;999px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#fff&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;box-shadow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;1px&lt;/span&gt; &lt;span class="mi"&gt;3px&lt;/span&gt; &lt;span class="nf"&gt;rgb&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;25&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;260ms&lt;/span&gt; &lt;span class="nf"&gt;cubic-bezier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Slide the knob
&lt;/h3&gt;

&lt;p&gt;When the input is checked, move the knob across the track. The distance is the track width minus the knob and both paddings.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.switch__input&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;checked&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nc"&gt;.switch__track&lt;/span&gt; &lt;span class="nc"&gt;.switch__knob&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateX&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;calc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--w&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;-&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;-&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--pad&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use &lt;code&gt;transform&lt;/code&gt;, not &lt;code&gt;left&lt;/code&gt;. It stays smooth because it avoids layout on every frame.&lt;/p&gt;

&lt;h3&gt;
  
  
  Change the track colour
&lt;/h3&gt;

&lt;p&gt;The track colour is the main on and off signal. Make it clear.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.switch__input&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;checked&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nc"&gt;.switch__track&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#17171c&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Check contrast between the knob and the track in both states. A pale grey off track on a white page can fail. A darker border on the track is a simple fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  Add the stretch: the detail that makes it feel alive
&lt;/h2&gt;

&lt;p&gt;A real knob does not teleport. A stretchy version widens while it travels, then snaps back to a circle when it lands. You can fake this with a short keyframe animation on the knob's width.&lt;/p&gt;

&lt;p&gt;The trick is that the knob must stretch toward where it is going. Moving right, it grows on its right edge. Moving left, it grows on its left edge. Two keyframe sets handle that, one per direction.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@keyframes&lt;/span&gt; &lt;span class="nt"&gt;stretch-on&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="mi"&gt;45&lt;/span&gt;&lt;span class="kt"&gt;%&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;calc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;1.35&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="k"&gt;@keyframes&lt;/span&gt; &lt;span class="nt"&gt;stretch-off&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="mi"&gt;45&lt;/span&gt;&lt;span class="kt"&gt;%&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;calc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;1.35&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nl"&gt;margin-left&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;calc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--knob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;-0&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;35&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nc"&gt;.switch__knob&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;animation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;stretch-off&lt;/span&gt; &lt;span class="mi"&gt;260ms&lt;/span&gt; &lt;span class="nf"&gt;cubic-bezier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.switch__input&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;checked&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nc"&gt;.switch__track&lt;/span&gt; &lt;span class="nc"&gt;.switch__knob&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;animation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;stretch-on&lt;/span&gt; &lt;span class="mi"&gt;260ms&lt;/span&gt; &lt;span class="nf"&gt;cubic-bezier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Keyframes with only a 45% step animate from and back to the knob's normal size. The knob is pinned by &lt;code&gt;left&lt;/code&gt;, so a wider knob grows rightward on the way on. On the way off, the negative &lt;code&gt;margin-left&lt;/code&gt; shifts the growth to the left edge. Because the animation name changes on each flip, the browser restarts it every time.&lt;/p&gt;

&lt;p&gt;Two trade-offs to know. Animating &lt;code&gt;width&lt;/code&gt; and &lt;code&gt;margin&lt;/code&gt; triggers layout, but on one small knob the cost is tiny. The off animation also plays once on page load, which most people never notice. If it bothers you, add a class to the switch after the first change and scope the animations to it.&lt;/p&gt;

&lt;p&gt;Keep the peak stretch between 1.2 and 1.4 times the knob size. Beyond that, it reads as a bug, not a feature.&lt;/p&gt;

&lt;p&gt;Timing guidance:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Part&lt;/th&gt;
&lt;th&gt;Duration&lt;/th&gt;
&lt;th&gt;Easing&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Knob travel&lt;/td&gt;
&lt;td&gt;220 to 300 ms&lt;/td&gt;
&lt;td&gt;Decelerating curve&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Stretch peak&lt;/td&gt;
&lt;td&gt;About 40 to 50% of the travel&lt;/td&gt;
&lt;td&gt;Same curve&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Track colour&lt;/td&gt;
&lt;td&gt;180 to 240 ms&lt;/td&gt;
&lt;td&gt;ease-out&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you want a springy settle instead, CSS &lt;code&gt;linear()&lt;/code&gt; can approximate a spring in pure CSS. Our guide on &lt;a href="https://crafttor.com/blog/css-linear-easing-function" rel="noopener noreferrer"&gt;CSS linear() easing&lt;/a&gt; shows how to build one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Accessibility: role, focus and reduced motion
&lt;/h2&gt;

&lt;p&gt;A toggle that looks great but fails a keyboard user is a broken toggle. Cover these three points.&lt;/p&gt;

&lt;h3&gt;
  
  
  Role and label
&lt;/h3&gt;

&lt;p&gt;You already have &lt;code&gt;role="switch"&lt;/code&gt; and a visible text label inside the &lt;code&gt;label&lt;/code&gt;. Clicking the text toggles the switch, and screen readers read the label. If the visible text is not enough context, add &lt;code&gt;aria-describedby&lt;/code&gt; pointing to a helper sentence.&lt;/p&gt;

&lt;h3&gt;
  
  
  Focus ring
&lt;/h3&gt;

&lt;p&gt;Because the input is hidden, show focus on the track instead:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.switch__input&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;focus-visible&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nc"&gt;.switch__track&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;outline&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2px&lt;/span&gt; &lt;span class="n"&gt;solid&lt;/span&gt; &lt;span class="mh"&gt;#fb9f3d&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;outline-offset&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;:focus-visible&lt;/code&gt; shows the ring for keyboard users without flashing it on every mouse click. Space toggles a native checkbox, so keyboard support comes for free.&lt;/p&gt;

&lt;h3&gt;
  
  
  Reduced motion
&lt;/h3&gt;

&lt;p&gt;Respect users who ask for less motion. Drop the stretch and shorten the slide, but keep the colour change.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@media&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nt"&gt;prefers-reduced-motion&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nt"&gt;reduce&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nc"&gt;.switch__knob&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;animation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;none&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nl"&gt;transition-duration&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1ms&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The state is still clear from the knob position and the track colour. Motion is decoration on top of that, never the only signal.&lt;/p&gt;

&lt;h3&gt;
  
  
  Quick accessibility checklist
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Native &lt;code&gt;input type="checkbox"&lt;/code&gt; with &lt;code&gt;role="switch"&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Visible text label inside the &lt;code&gt;label&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Focus ring on &lt;code&gt;:focus-visible&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] On and off states differ by more than colour alone (knob position)&lt;/li&gt;
&lt;li&gt;[ ] Contrast checked in both states&lt;/li&gt;
&lt;li&gt;[ ] Reduced-motion fallback in place&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A ready version: the Stretch Toggle in the Capture Motion gallery
&lt;/h2&gt;

&lt;p&gt;Building it yourself is a good way to learn the parts. If you would rather start from a finished piece, the &lt;a href="https://capturemotion.dev?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=growth_engine" rel="noopener noreferrer"&gt;Capture Motion&lt;/a&gt; gallery has a Stretch Toggle. The knob leans toward where it is going, stretches on the way, and inverts the track as it lands.&lt;/p&gt;

&lt;p&gt;From the gallery, you can customize it and then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Send it to Figma&lt;/strong&gt; as a Figma Motion timeline, with the keyframes and easing on tracks you can edit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Copy it as code&lt;/strong&gt; in CSS, Framer Motion or GSAP, or download it as HTML and React.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It sits next to other interactive components in the gallery. If you like the stretch idea, the &lt;a href="https://crafttor.com/blog/liquid-tabs-animation" rel="noopener noreferrer"&gt;liquid tabs animation&lt;/a&gt; uses the same leading-edge principle on a tab indicator. For a bigger gesture on a confirm action, see the &lt;a href="https://crafttor.com/blog/slide-to-confirm-button-animation" rel="noopener noreferrer"&gt;slide to confirm button animation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Seen a toggle on another site that you want to study? The Capture Motion extension can record its real keyframes, durations and easing, then export them to code or &lt;a href="https://capturemotion.dev?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=growth_engine" rel="noopener noreferrer"&gt;Figma&lt;/a&gt;. Capture or rebuild only designs you own or have permission to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Should a toggle switch use a checkbox or a button?
&lt;/h3&gt;

&lt;p&gt;A checkbox with &lt;code&gt;role="switch"&lt;/code&gt; is the simplest robust choice. It works in forms, supports the Space key and reports its state. A &lt;code&gt;button&lt;/code&gt; with &lt;code&gt;aria-pressed&lt;/code&gt; also works, but you have to handle the state in JavaScript.&lt;/p&gt;

&lt;h3&gt;
  
  
  How long should a toggle switch animation be?
&lt;/h3&gt;

&lt;p&gt;Around 220 to 300 ms for the knob travel. Shorter feels abrupt, longer feels sluggish on a control people flip often.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I make the knob stretch while it moves?
&lt;/h3&gt;

&lt;p&gt;Animate &lt;code&gt;scaleX&lt;/code&gt; or the knob width with a short keyframe that peaks near the middle of the move. Set &lt;code&gt;transform-origin&lt;/code&gt; so the knob grows toward its direction of travel.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I keep the animation accessible?
&lt;/h3&gt;

&lt;p&gt;Use a native checkbox with &lt;code&gt;role="switch"&lt;/code&gt;, a visible label, a &lt;code&gt;:focus-visible&lt;/code&gt; ring and a &lt;code&gt;prefers-reduced-motion&lt;/code&gt; fallback. Make sure the on state is clear from the knob position, not just colour.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there a ready-made animated toggle I can use?
&lt;/h3&gt;

&lt;p&gt;Yes. The Stretch Toggle in the Capture Motion gallery can be sent to Figma as a Figma Motion timeline or copied as code.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>css</category>
      <category>design</category>
    </item>
    <item>
      <title>Button Hover Animation CSS: Fill Sweep, Lift, Arrow Nudge and Glow</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Fri, 13 Nov 2026 04:37:02 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/button-hover-animation-css-fill-sweep-lift-arrow-nudge-and-glow-92k</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/button-hover-animation-css-fill-sweep-lift-arrow-nudge-and-glow-92k</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/button-hover-animation-css" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; A good button hover animation in CSS is short, eased and honest about what the button does. Use 150 to 300 ms, an ease-out curve, and animate only &lt;code&gt;transform&lt;/code&gt;, &lt;code&gt;opacity&lt;/code&gt; and colour where you can. Below are four effects with code and the timing that makes them feel right. You also get a reduced-motion fallback and a faster way to copy a hover you like.&lt;/p&gt;

&lt;p&gt;Buttons are the most hovered element on any page. A small, well-timed response tells the user "this is clickable, and it is ready". A slow or bouncy one feels laggy. The difference is rarely the effect itself. It is almost always the duration and the easing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with a solid base button
&lt;/h2&gt;

&lt;p&gt;Every effect below builds on the same base. Keep the transition on the base rule, not the &lt;code&gt;:hover&lt;/code&gt; rule, so it plays both ways.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.btn&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;relative&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;display&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;inline-flex&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;align-items&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;center&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;gap&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;8px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;padding&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;12px&lt;/span&gt; &lt;span class="mi"&gt;20px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;border&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;10px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#17171c&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;color&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#fff&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;font&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;600&lt;/span&gt; &lt;span class="mi"&gt;15px&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="n"&gt;system-ui&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;sans-serif&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;cursor&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;pointer&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;200ms&lt;/span&gt; &lt;span class="nf"&gt;cubic-bezier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
              &lt;span class="n"&gt;box-shadow&lt;/span&gt; &lt;span class="mi"&gt;200ms&lt;/span&gt; &lt;span class="nf"&gt;cubic-bezier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
              &lt;span class="n"&gt;background-color&lt;/span&gt; &lt;span class="mi"&gt;200ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;List each property in &lt;code&gt;transition&lt;/code&gt;. Writing &lt;code&gt;transition: all&lt;/code&gt; is tempting, but it animates things you did not plan, like a width change from a font swap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four button hover animation CSS effects
&lt;/h2&gt;

&lt;p&gt;Each effect suits a different job. Pick one per button style, not all four at once.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Fill sweep
&lt;/h3&gt;

&lt;p&gt;A colour fills the button from one side. It reads as "you are about to commit to this", which suits primary actions.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.btn-sweep&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;overflow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;hidden&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;isolation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;isolate&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.btn-sweep&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;before&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;absolute&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;inset&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;z-index&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;-1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#fb9f3d&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;scaleX&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transform-origin&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;left&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;260ms&lt;/span&gt; &lt;span class="nf"&gt;cubic-bezier&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.btn-sweep&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;before&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;scaleX&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Animating &lt;code&gt;scaleX&lt;/code&gt; on a pseudo-element is cheaper than animating &lt;code&gt;width&lt;/code&gt; or &lt;code&gt;background-position&lt;/code&gt;. The browser can run it on the compositor. If the text colour changes too, check contrast on both the start and end colours.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Lift and shadow
&lt;/h3&gt;

&lt;p&gt;The button rises a few pixels and its shadow grows. It feels physical, and it works well on cards and secondary buttons.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.btn-lift&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateY&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;-2px&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;box-shadow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;8px&lt;/span&gt; &lt;span class="mi"&gt;20px&lt;/span&gt; &lt;span class="nf"&gt;rgb&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;18&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.btn-lift&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;active&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateY&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;box-shadow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;2px&lt;/span&gt; &lt;span class="mi"&gt;6px&lt;/span&gt; &lt;span class="nf"&gt;rgb&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;18&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transition-duration&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;80ms&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Keep the lift small: 1 to 3 px. Larger lifts make a row of buttons look jumpy. The &lt;code&gt;:active&lt;/code&gt; rule gives a quick press back down, which closes the loop.&lt;/p&gt;

&lt;p&gt;Animating &lt;code&gt;box-shadow&lt;/code&gt; repaints on every frame. On one button it is fine. On a grid of fifty cards, put the larger shadow on a pseudo-element and fade its &lt;code&gt;opacity&lt;/code&gt; instead.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Arrow nudge
&lt;/h3&gt;

&lt;p&gt;An arrow icon slides a few pixels in the direction of travel. It is the quietest of the four and suits links like "Read more" or "Next".&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.btn-arrow&lt;/span&gt; &lt;span class="nt"&gt;svg&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;180ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.btn-arrow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt; &lt;span class="nt"&gt;svg&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateX&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;4px&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Put the &lt;code&gt;:hover&lt;/code&gt; on the button, not on the icon. The button is the bigger target, and the user hovers it first. This is the "hover the container, move the child" pattern.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Glow
&lt;/h3&gt;

&lt;p&gt;A soft, coloured halo appears behind the button. It works on dark backgrounds and for one hero call to action per page.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.btn-glow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;after&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;absolute&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;inset&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;-6px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;z-index&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;-1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;14px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#fb9f3d&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;blur&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;14px&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;opacity&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;opacity&lt;/span&gt; &lt;span class="mi"&gt;240ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;.btn-glow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;after&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;opacity&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;55&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The blur is set once and never animated. Only &lt;code&gt;opacity&lt;/code&gt; changes, which keeps it smooth. Animating &lt;code&gt;filter: blur()&lt;/code&gt; directly is much heavier.&lt;/p&gt;

&lt;h2&gt;
  
  
  Timing and easing: the part that makes it feel right
&lt;/h2&gt;

&lt;p&gt;Most hover problems are timing problems. Use this table as a starting point.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Effect&lt;/th&gt;
&lt;th&gt;Duration&lt;/th&gt;
&lt;th&gt;Easing&lt;/th&gt;
&lt;th&gt;Notes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Fill sweep&lt;/td&gt;
&lt;td&gt;220 to 300 ms&lt;/td&gt;
&lt;td&gt;&lt;code&gt;cubic-bezier(.22, 1, .36, 1)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Larger area, so slightly longer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lift and shadow&lt;/td&gt;
&lt;td&gt;150 to 220 ms&lt;/td&gt;
&lt;td&gt;ease-out&lt;/td&gt;
&lt;td&gt;Press back in about 80 ms&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Arrow nudge&lt;/td&gt;
&lt;td&gt;150 to 200 ms&lt;/td&gt;
&lt;td&gt;ease-out&lt;/td&gt;
&lt;td&gt;Small distance, short time&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Glow&lt;/td&gt;
&lt;td&gt;200 to 260 ms&lt;/td&gt;
&lt;td&gt;ease-out&lt;/td&gt;
&lt;td&gt;Fade only&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A few rules hold across all four:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Stay between 150 and 300 ms.&lt;/strong&gt; Under 100 ms, the user barely sees it. Over 300 ms, the button feels slow to respond.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use ease-out for entering.&lt;/strong&gt; The motion starts fast and settles, so the button answers the pointer right away.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Leave faster than you enter.&lt;/strong&gt; A hover-out at about two thirds of the hover-in time feels tidy. Put a second &lt;code&gt;transition&lt;/code&gt; on the &lt;code&gt;:hover&lt;/code&gt; rule to make them differ.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid bouncy springs on buttons.&lt;/strong&gt; Overshoot is fun on toggles and tabs. On a button you hover many times a day, it gets tiring.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To make the exit faster than the entry:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.btn&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;140ms&lt;/span&gt; &lt;span class="n"&gt;ease-in&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;          &lt;span class="cm"&gt;/* leaving */&lt;/span&gt;
&lt;span class="nc"&gt;.btn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;transition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt; &lt;span class="mi"&gt;220ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;   &lt;span class="cm"&gt;/* entering */&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The rule that applies is the one for the state you are moving into. That is why the faster value sits on the base rule.&lt;/p&gt;

&lt;p&gt;If you want to go deeper on curves, our guide to &lt;a href="https://crafttor.com/blog/css-easing-functions-explained" rel="noopener noreferrer"&gt;CSS easing functions explained&lt;/a&gt; covers &lt;code&gt;cubic-bezier()&lt;/code&gt; and &lt;code&gt;steps()&lt;/code&gt; with examples.&lt;/p&gt;

&lt;h2&gt;
  
  
  Respect reduced motion and touch screens
&lt;/h2&gt;

&lt;p&gt;Some users ask their system for less motion. Honour that with a media query. Keep the colour change, drop the movement.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@media&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nt"&gt;prefers-reduced-motion&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nt"&gt;reduce&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nc"&gt;.btn&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nc"&gt;.btn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;before&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nc"&gt;.btn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;after&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nc"&gt;.btn&lt;/span&gt; &lt;span class="n"&gt;svg&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;transition-property&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;opacity&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;background-color&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;color&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="nc"&gt;.btn-lift&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;hover&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nc"&gt;.btn-arrow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;hover&lt;/span&gt; &lt;span class="n"&gt;svg&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;none&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On phones, a tap can leave a hover style stuck until the user taps elsewhere. Wrap hover-only motion in a hover media query:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@media&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nt"&gt;hover&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nt"&gt;and&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nt"&gt;pointer&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nt"&gt;fine&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nc"&gt;.btn-lift&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;hover&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;translateY&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;-2px&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two more checks before you ship:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Give &lt;code&gt;:focus-visible&lt;/code&gt; the same visual change as &lt;code&gt;:hover&lt;/code&gt;, so keyboard users get the same feedback.&lt;/li&gt;
&lt;li&gt;Never rely on motion alone to show state. A disabled button should look disabled even with no animation.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Copy a hover you like instead of guessing the values
&lt;/h2&gt;

&lt;p&gt;You often see a button hover on a real site and want the same feel. Guessing is slow. You eyeball 200 ms, it turns out to be 320 ms, and the easing was a custom curve you would never have picked.&lt;/p&gt;

&lt;p&gt;DevTools can help when the hover is a plain CSS transition. Force &lt;code&gt;:hover&lt;/code&gt; in the Styles pane and read the rule. It gets harder when the hover is started by JavaScript, uses GSAP, or animates several layers with different delays. Our walkthrough on &lt;a href="https://crafttor.com/blog/how-to-capture-hover-animations" rel="noopener noreferrer"&gt;how to capture hover animations&lt;/a&gt; covers each case.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://capturemotion.dev?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=growth_engine" rel="noopener noreferrer"&gt;Capture Motion&lt;/a&gt; reads the real values for you:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the page in Chrome and start the Capture Motion extension.&lt;/li&gt;
&lt;li&gt;Pick the button, or its container if an inner icon moves too.&lt;/li&gt;
&lt;li&gt;Play the hover. The extension triggers a real &lt;code&gt;:hover&lt;/code&gt; state through the Chrome DevTools Protocol, attached only during the capture.&lt;/li&gt;
&lt;li&gt;Preview the capture. You see each animated property with its keyframes, duration, delay and easing.&lt;/li&gt;
&lt;li&gt;Export it. With a free account, copy the CSS, Framer Motion or GSAP code, or send it to Figma as a Figma Motion timeline.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It records CSS transitions and keyframes, the Web Animations API, GSAP and Lottie. That covers the cases where DevTools shows no timing to read. Capture or rebuild only designs you own or have permission to use. Take the timing and easing, then apply them to your own button.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick checklist before you ship
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Duration between 150 and 300 ms&lt;/li&gt;
&lt;li&gt;[ ] Ease-out on enter, slightly faster exit&lt;/li&gt;
&lt;li&gt;[ ] Only &lt;code&gt;transform&lt;/code&gt;, &lt;code&gt;opacity&lt;/code&gt; and colours animate&lt;/li&gt;
&lt;li&gt;[ ] &lt;code&gt;:focus-visible&lt;/code&gt; matches &lt;code&gt;:hover&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Reduced-motion fallback in place&lt;/li&gt;
&lt;li&gt;[ ] Hover motion wrapped in &lt;code&gt;@media (hover: hover)&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Contrast checked at both ends of a colour change&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Want a ready example with stagger and hover? See the &lt;a href="https://crafttor.com/blog/animated-avatar-stack" rel="noopener noreferrer"&gt;animated avatar stack&lt;/a&gt; build, or browse the gallery on &lt;a href="https://capturemotion.dev?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=growth_engine" rel="noopener noreferrer"&gt;capturemotion.dev&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is a good duration for a button hover animation in CSS?
&lt;/h3&gt;

&lt;p&gt;Between 150 and 300 ms covers almost every case. Small moves like an arrow nudge sit near 150 to 200 ms. Larger fills can run to 300 ms. Past that, the button starts to feel slow.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which easing should I use for button hovers?
&lt;/h3&gt;

&lt;p&gt;Use ease-out or a curve like &lt;code&gt;cubic-bezier(.22, 1, .36, 1)&lt;/code&gt; for the hover-in. It responds instantly and settles gently. For the hover-out, a slightly shorter ease-in or ease-out works well.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does my hover animation stutter?
&lt;/h3&gt;

&lt;p&gt;You are probably animating layout or paint properties like &lt;code&gt;width&lt;/code&gt;, &lt;code&gt;top&lt;/code&gt; or &lt;code&gt;filter&lt;/code&gt;. Switch to &lt;code&gt;transform&lt;/code&gt; and &lt;code&gt;opacity&lt;/code&gt;. For shadows and glows, animate the opacity of a pseudo-element that already has the shadow.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I make hover-out faster than hover-in?
&lt;/h3&gt;

&lt;p&gt;Put the faster &lt;code&gt;transition&lt;/code&gt; on the base rule and the slower one on the &lt;code&gt;:hover&lt;/code&gt; rule. The browser uses the transition of the state the element is moving into.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I copy the exact hover timing from another website?
&lt;/h3&gt;

&lt;p&gt;Yes. For plain CSS, force &lt;code&gt;:hover&lt;/code&gt; in Chrome DevTools and read the rule. For JavaScript or GSAP hovers, a capture tool like Capture Motion records the real keyframes, durations and easing. Only copy from sites you own or have permission to use.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>css</category>
      <category>design</category>
    </item>
    <item>
      <title>Five Things That Break When You Convert a PSD to Figma (and How to Handle Each)</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Wed, 04 Nov 2026 10:31:42 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/five-things-that-break-when-you-convert-a-psd-to-figma-and-how-to-handle-each-2k7c</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/five-things-that-break-when-you-convert-a-psd-to-figma-and-how-to-handle-each-2k7c</guid>
      <description>&lt;p&gt;Converting a PSD to Figma sounds like a file-format problem. It is really a &lt;em&gt;feature-matching&lt;/em&gt; problem: Photoshop can do things Figma has no word for. Here are the five places an import actually goes sideways, and what to do about each one. This comes from building and running the &lt;a href="https://www.figma.com/community/plugin/1687850435434962649" rel="noopener noreferrer"&gt;PSD to Figma&lt;/a&gt; plugin, so the fixes are the ones we ship.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhwdya2vkzhv93hhd316u.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhwdya2vkzhv93hhd316u.jpg" alt="Five things that break" width="800" height="380"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The font is not on your machine
&lt;/h2&gt;

&lt;p&gt;A PSD &lt;em&gt;references&lt;/em&gt; fonts. It does not contain them. If Figma cannot find the font, the text has to fall back to something else.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do:&lt;/strong&gt; install the font before importing. If you cannot, the plugin falls back to Inter and &lt;strong&gt;names the missing font in the import report&lt;/strong&gt;, so you know exactly which one to install. Swap it later and the lines settle.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Adjustment layers
&lt;/h2&gt;

&lt;p&gt;Curves, Levels, Hue/Saturation. Figma has no adjustment layers at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do:&lt;/strong&gt; accept that the effect gets &lt;em&gt;rendered into the layer below&lt;/em&gt; and listed in the report. If you need the original adjustability, keep the PSD as the source of truth, or import that layer group as an image on purpose.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Bevel &amp;amp; Emboss and other layer styles with no twin
&lt;/h2&gt;

&lt;p&gt;Drop shadows, inner shadows, glows, strokes and overlays map to Figma effects. Bevel &amp;amp; Emboss does not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do:&lt;/strong&gt; let the plugin bake those layers as images and read the report to see which layers were affected. Everything else stays an editable effect, so the shadow on your button is still a shadow you can change.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Images over 4096 pixels
&lt;/h2&gt;

&lt;p&gt;Figma will not accept an image larger than 4096 pixels on a side. A big Photoshop canvas can easily exceed that, and a naive converter fails with an error that tells you nothing useful.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do:&lt;/strong&gt; the plugin downscales oversized layers to fit before handing them to Figma, so the import completes. Keep a copy of the original if you need full resolution for print, and export back to PSD from Figma when you do.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Text that was rasterised for an effect
&lt;/h2&gt;

&lt;p&gt;If a designer rasterised a headline to add a filter, the text is gone. It is pixels. No converter can recover it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do:&lt;/strong&gt; ask the sender for a version with live text, or keep an unrasterised copy on a hidden layer. The plugin imports hidden layers too, with visibility off, so a spare copy survives the trip.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pick the right depth for the job
&lt;/h2&gt;

&lt;p&gt;You do not always want everything editable. The plugin has four import modes, and each costs a small number of credits:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Mode&lt;/th&gt;
&lt;th&gt;What you get&lt;/th&gt;
&lt;th&gt;Credits&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Fully editable&lt;/td&gt;
&lt;td&gt;Live text, shapes, masks, gradients, styles&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Editable text&lt;/td&gt;
&lt;td&gt;Live text, everything else as images&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Layers as images&lt;/td&gt;
&lt;td&gt;Each layer as pixels, structure kept&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Flattened&lt;/td&gt;
&lt;td&gt;One image&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For reference artwork, Flattened is plenty. For a template your team will edit all year, Fully editable is the right call.&lt;/p&gt;

&lt;h2&gt;
  
  
  About privacy
&lt;/h2&gt;

&lt;p&gt;The PSD is parsed inside the plugin sandbox on your computer. The artwork is never uploaded. The plugin sends limited usage details to Crafttor: the action, its mode, and the file or frame name and size.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on your worst file
&lt;/h2&gt;

&lt;p&gt;Drop your ugliest PSD on the plugin. You get a preview with no account. Press &lt;strong&gt;Login to Generate&lt;/strong&gt; when you want it in Figma, and you start with 5 free credits.&lt;/p&gt;

&lt;p&gt;Longer guides on Crafttor:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://crafttor.com/blog/convert-psd-to-figma" rel="noopener noreferrer"&gt;How to convert PSD to Figma, step by step&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://crafttor.com/blog/photoshop-layer-effects-in-figma" rel="noopener noreferrer"&gt;Photoshop layer effects in Figma&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://crafttor.com/blog/how-to-choose-a-psd-to-figma-plugin" rel="noopener noreferrer"&gt;7 questions to ask before you buy a PSD to Figma plugin&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>figma</category>
      <category>design</category>
      <category>photoshop</category>
      <category>tools</category>
    </item>
    <item>
      <title>WEBP to Figma: Convert WEBP Images into Editable Layers</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Mon, 02 Nov 2026 08:27:59 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/webp-to-figma-convert-webp-images-into-editable-layers-56ic</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/webp-to-figma-convert-webp-images-into-editable-layers-56ic</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/webp-to-figma" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;WEBP to Figma is a question that comes up more often every year. Websites serve more and more images as WEBP, and many tools now save files in that format by default. You right click a web graphic, save it, and end up with a .webp file. Now you want it as something you can edit.&lt;/p&gt;

&lt;p&gt;Image to Figma Design accepts WEBP directly, alongside PNG and JPEG. You do not need to convert the file to another format first. This guide explains what to know about WEBP specifically, how to get a good result, and when a different source image will serve you better.&lt;/p&gt;

&lt;h2&gt;
  
  
  What makes WEBP different
&lt;/h2&gt;

&lt;p&gt;WEBP is an image format designed for the web. Its job is to keep files small so pages load fast. It supports both lossy compression, like JPEG, and lossless compression, like PNG. It can also hold transparency.&lt;/p&gt;

&lt;p&gt;For conversion, the key question is which kind of WEBP you have:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lossless WEBP&lt;/strong&gt; keeps every pixel. It converts as well as a PNG of the same size.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lossy WEBP&lt;/strong&gt; throws away some detail to save space. Heavy compression can soften text edges and create blotchy areas around shapes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You often cannot tell which kind you have from the file name. Zoom in on small text. If edges look crisp, you are fine. If they look smeared, see the tips below.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where WEBP files usually come from
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Images saved from websites and online shops&lt;/li&gt;
&lt;li&gt;Exports from design and image tools that default to WEBP&lt;/li&gt;
&lt;li&gt;Screenshots shared through some chat apps and content systems&lt;/li&gt;
&lt;li&gt;Marketing assets compressed for a site&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each source has a different quality level. A WEBP saved from a product page may have been resized and compressed for speed, not for editing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step by step: WEBP to Figma
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Find the largest version available.&lt;/strong&gt; Web images are often resized. If you can get a bigger version of the same image, use it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zoom in to check quality.&lt;/strong&gt; Look at the smallest text in the image. Crisp text converts more accurately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open Figma and run Image to Figma Design.&lt;/strong&gt; Sign in with your free Crafttor account if prompted.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add the WEBP.&lt;/strong&gt; Drag and drop the file, browse for it, or copy it and paste with Cmd+V or Ctrl+V.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick a mode.&lt;/strong&gt; Fast costs 1 credit and gives a quick editable copy. Turbo AI costs 2 credits and rebuilds the layout as nested auto-layout frames.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Convert.&lt;/strong&gt; The result lands on your canvas as editable text layers, shapes, images, and icons.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the details.&lt;/strong&gt; Check text that sat on photos or gradients, since those areas are the hardest to read.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Getting a better result from a lossy WEBP
&lt;/h2&gt;

&lt;p&gt;Sometimes the WEBP you have is all you have. A few habits help.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Take a fresh screenshot instead.&lt;/strong&gt; If the image came from a live page, a screenshot of the page at a normal zoom is often sharper than the compressed file. Capture at 1x to 2x of the real UI. The &lt;a href="https://crafttor.com/blog/website-screenshot-to-figma" rel="noopener noreferrer"&gt;website screenshot to Figma guide&lt;/a&gt; covers capture tips.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do not upscale blindly.&lt;/strong&gt; Making a small, blurry image bigger does not add real detail. A clean source matters more than a big one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do not convert to PNG and expect a fix.&lt;/strong&gt; Saving a lossy WEBP as PNG keeps the same lost detail. Since the plugin reads WEBP directly, there is no need for that step.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Crop to what you need.&lt;/strong&gt; If only one card or section matters, crop to it. A focused image gives a cleaner result with less cleanup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Transparency in WEBP files
&lt;/h2&gt;

&lt;p&gt;Some WEBP files have transparent backgrounds, such as logos or product cutouts. These are usually artwork rather than UI. They tend to come through as image layers, which is often what you want.&lt;/p&gt;

&lt;p&gt;If you are converting a UI image and it has a transparent background, consider placing it on a solid background first. Clear contrast helps the converter find edges.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fast or Turbo AI for WEBP images?
&lt;/h2&gt;

&lt;p&gt;The format does not change the choice. What matters is the content.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fast&lt;/strong&gt; for banners, ads, cards, and graphics where you mainly edit text and colors.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Turbo AI&lt;/strong&gt; for full screens and page sections where you want resizable, nested auto-layout.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you are unsure, the &lt;a href="https://crafttor.com/blog/fast-vs-turbo-ai" rel="noopener noreferrer"&gt;Fast vs Turbo AI guide&lt;/a&gt; breaks it down.&lt;/p&gt;

&lt;h2&gt;
  
  
  WEBP to HTML
&lt;/h2&gt;

&lt;p&gt;Sometimes the end goal is code, not a Figma file. The plugin can also give you a downloadable HTML file instead of placing layers. This is handy when you want a quick coded starting point from a web image. The &lt;a href="https://crafttor.com/blog/screenshot-to-html" rel="noopener noreferrer"&gt;screenshot to HTML guide&lt;/a&gt; explains what to expect from that output.&lt;/p&gt;

&lt;h2&gt;
  
  
  PNG, JPEG, or WEBP: does it matter?
&lt;/h2&gt;

&lt;p&gt;All three work. The real difference is quality, not format.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A sharp PNG and a lossless WEBP of the same screen will behave alike.&lt;/li&gt;
&lt;li&gt;A heavily compressed JPEG and a lossy WEBP share the same risks.&lt;/li&gt;
&lt;li&gt;A large, clean image beats a small, compressed one in any format.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you have a choice of source, pick the sharpest version. For format specific tips, see &lt;a href="https://crafttor.com/blog/png-to-figma" rel="noopener noreferrer"&gt;PNG to Figma&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use images you have rights to
&lt;/h2&gt;

&lt;p&gt;Images saved from websites belong to someone. Convert WEBP files you own or have permission to use, and rebuild third party designs for study only, not to ship copies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest limitations
&lt;/h2&gt;

&lt;p&gt;Very busy illustrations, heavy gradients, and blurry or low resolution images reduce accuracy. Heavily compressed WEBP files fall into that last group. Complex screens may need light cleanup in either mode.&lt;/p&gt;

&lt;h2&gt;
  
  
  Convert your first WEBP
&lt;/h2&gt;

&lt;p&gt;You do not need any extra tool to change formats. &lt;a href="https://www.figma.com/community/plugin/1417763374654877658?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=webp-to-figma" rel="noopener noreferrer"&gt;Install Image to Figma Design&lt;/a&gt; and drop in a WEBP. It works on every Figma plan, including the free Starter plan, and logged-in users get free daily credits.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does Image to Figma Design support WEBP?
&lt;/h3&gt;

&lt;p&gt;Yes. The plugin accepts PNG, JPEG, and WEBP images. You can drag in a WEBP, browse for it, or paste it directly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need to convert WEBP to PNG first?
&lt;/h3&gt;

&lt;p&gt;No. The plugin reads WEBP directly. Converting a lossy WEBP to PNG does not restore lost detail, so it adds a step without improving the result.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does my WEBP convert less accurately than a screenshot?
&lt;/h3&gt;

&lt;p&gt;Many web WEBP files are resized and compressed for speed. Soft text edges reduce accuracy. A fresh screenshot of the live page at 1x to 2x often works better.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I get HTML from a WEBP image?
&lt;/h3&gt;

&lt;p&gt;Yes. Instead of placing layers on the canvas, the plugin can give you a downloadable HTML file.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will transparent WEBP images convert?
&lt;/h3&gt;

&lt;p&gt;They will, but transparent cutouts like logos usually come through as image layers. For UI images, a solid background helps the converter find edges.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>design</category>
      <category>images</category>
    </item>
    <item>
      <title>Screenshot to Responsive HTML: From One Image to Every Screen</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Mon, 02 Nov 2026 08:26:57 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/screenshot-to-responsive-html-from-one-image-to-every-screen-31e7</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/screenshot-to-responsive-html-from-one-image-to-every-screen-31e7</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/screenshot-to-responsive-html" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Going from screenshot to responsive HTML has a catch that many tools gloss over. A screenshot shows one screen at one width. It does not say what should happen on a phone, a tablet, or a wide monitor. Any tool that converts an image to HTML has to guess, or give you a fixed layout that you then make responsive.&lt;/p&gt;

&lt;p&gt;That is not a reason to skip conversion. It is a reason to plan the second step. This guide shows how to get clean HTML from a screenshot with Image to Figma Design, and how to make it responsive without rewriting it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a screenshot can and cannot tell you
&lt;/h2&gt;

&lt;p&gt;A screenshot gives you a lot: text, colors, sizes, positions, and the visual grouping of elements. It cannot give you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Breakpoints.&lt;/strong&gt; Where the layout should change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fluid behavior.&lt;/strong&gt; Which elements stretch and which stay fixed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hidden content.&lt;/strong&gt; Menus, hover states, and collapsed sections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Semantics.&lt;/strong&gt; Which text is a heading, a link, or a button in code.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the conversion gives you the visual layout. You decide how it adapts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two routes from image to HTML
&lt;/h2&gt;

&lt;p&gt;The plugin can output a downloadable HTML file instead of placing layers. You can also convert to Figma layers first, refine there, and then build or export the code. Pick based on your goal:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Direct HTML&lt;/strong&gt; is fastest when you want a working page to tweak in code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Figma first&lt;/strong&gt; is better when the design needs review or changes before anyone writes code.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 1: Capture for HTML
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Capture at a common desktop width, at 1x to 2x of the real UI.&lt;/li&gt;
&lt;li&gt;For long pages, capture section by section. Each section converts more cleanly than one tall image.&lt;/li&gt;
&lt;li&gt;If you already have a mobile design, capture it too. It answers the breakpoint question for you.&lt;/li&gt;
&lt;li&gt;Remove browser chrome, popups, and cookie banners.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 2: Choose Turbo AI for structure
&lt;/h2&gt;

&lt;p&gt;Mode choice matters more for HTML than for anything else.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Turbo AI&lt;/strong&gt; (2 credits) rebuilds the screen as nested auto-layout frames. Nested rows and columns translate naturally to flex containers, which are much easier to make responsive.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fast&lt;/strong&gt; (1 credit) produces positioned layers. That is great for quick edits in Figma, but positioned layouts are harder to adapt to new widths.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If responsive HTML is the goal, start with Turbo AI. For more on the trade-off, see &lt;a href="https://crafttor.com/blog/fast-vs-turbo-ai" rel="noopener noreferrer"&gt;Fast vs Turbo AI&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Convert and download
&lt;/h2&gt;

&lt;p&gt;Open the plugin, add your screenshot by pasting, dragging, or browsing, and choose the HTML output. Download the file and open it in a browser. Compare it with the original screenshot at the same width.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Make it responsive
&lt;/h2&gt;

&lt;p&gt;Now open the HTML in your editor. Work through this checklist.&lt;/p&gt;

&lt;h3&gt;
  
  
  Replace fixed widths with fluid ones
&lt;/h3&gt;

&lt;p&gt;Find containers with fixed pixel widths. Change outer containers to a max-width with width 100 percent. Change inner columns to flexible sizes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Let rows wrap or stack
&lt;/h3&gt;

&lt;p&gt;For rows of cards or columns, add wrapping, or switch the direction to a column below a breakpoint. A simple rule: if items would get narrower than a comfortable reading width, stack them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Add two or three breakpoints
&lt;/h3&gt;

&lt;p&gt;You rarely need many. A mobile breakpoint and a tablet breakpoint cover most layouts. Test by dragging your browser window narrower and noting where things break. Add a breakpoint there.&lt;/p&gt;

&lt;h3&gt;
  
  
  Scale typography
&lt;/h3&gt;

&lt;p&gt;Large headlines that look right on desktop overflow on mobile. Reduce heading sizes at the mobile breakpoint, or use a clamp-based fluid size.&lt;/p&gt;

&lt;h3&gt;
  
  
  Make images flexible
&lt;/h3&gt;

&lt;p&gt;Set images to a max-width of 100 percent and height auto. For decorative images, consider hiding them on small screens.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fix semantics
&lt;/h3&gt;

&lt;p&gt;Turn heading text into proper heading tags, buttons into button elements, and links into anchors. This improves accessibility and SEO.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Test at real sizes
&lt;/h2&gt;

&lt;p&gt;Check the page at a phone width, a tablet width, and a wide desktop. Use your browser's device toolbar. Look for overflowing text, buttons too small to tap, and images that push the layout sideways.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to go through Figma first
&lt;/h2&gt;

&lt;p&gt;If the screenshot is from an old version you want to improve, convert to Figma layers first. Make the design changes there. You can even build a mobile frame next to the desktop one, so the responsive behavior is designed, not guessed. Then build the HTML. Our guide on &lt;a href="https://crafttor.com/blog/screenshot-to-html" rel="noopener noreferrer"&gt;screenshot to HTML&lt;/a&gt; covers the basics of the direct route, and &lt;a href="https://crafttor.com/blog/screenshot-to-figma-for-developers" rel="noopener noreferrer"&gt;screenshot to Figma for developers&lt;/a&gt; covers the Figma side.&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest limits
&lt;/h2&gt;

&lt;p&gt;Generated HTML is a strong first draft, not production code. Busy illustrations and heavy gradients often come through as images. Low-resolution or blurry screenshots reduce text accuracy. Interactive behavior, forms, and data still need real code.&lt;/p&gt;

&lt;p&gt;Convert pages you own or have permission to use. For pages you study, rebuild for learning and do not ship copies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on a real page
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.figma.com/community/plugin/1417763374654877658?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=screenshot-to-responsive-html" rel="noopener noreferrer"&gt;Install Image to Figma Design&lt;/a&gt; and convert your first screenshot to HTML. It runs on every Figma plan, including the free Starter plan, and logged-in users get free daily credits.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can a screenshot be converted directly into responsive HTML?
&lt;/h3&gt;

&lt;p&gt;A screenshot shows only one width, so any converter has to guess the responsive behavior. Convert first, then add fluid widths and breakpoints yourself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which mode gives the best HTML for responsive work?
&lt;/h3&gt;

&lt;p&gt;Turbo AI, because it rebuilds the screen as nested auto-layout frames, which translate to flex containers that adapt more easily.&lt;/p&gt;

&lt;h3&gt;
  
  
  How many breakpoints should I add?
&lt;/h3&gt;

&lt;p&gt;Usually two or three. Drag the browser narrower and add a breakpoint wherever the layout starts to break.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is the HTML ready for production?
&lt;/h3&gt;

&lt;p&gt;Treat it as a first draft. Add semantics, interactions, and accessibility checks before you ship.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I convert a long landing page?
&lt;/h3&gt;

&lt;p&gt;Yes. Capture and convert it section by section for cleaner output, then combine the sections in your code.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>css</category>
      <category>html</category>
    </item>
    <item>
      <title>Screenshot to Figma for Developers: A Practical Guide</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Sat, 31 Oct 2026 06:28:24 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/screenshot-to-figma-for-developers-a-practical-guide-334j</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/screenshot-to-figma-for-developers-a-practical-guide-334j</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/screenshot-to-figma-for-developers" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;This guide covers screenshot to Figma for developers who need design answers without a designer on hand. Maybe you are a solo developer building a side project. Maybe you joined a team where the design files are outdated. Or you need to fix a screen and all you have is a bug report with a screenshot.&lt;/p&gt;

&lt;p&gt;In all these cases, a flat image is hard to work from. You cannot read exact text, check spacing, or try a change. Converting the screenshot into editable Figma layers fixes that, and it takes a couple of minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Developer use cases that actually come up
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rebuilding a screen with no source file.&lt;/strong&gt; You have the production UI, but no design. You want a reference you can measure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reproducing a bug report.&lt;/strong&gt; A user sent a screenshot of a broken layout. You want to annotate it and compare against the intended design.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quick mockups for a PR.&lt;/strong&gt; You want to show a reviewer a proposed change before writing the code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prototyping from an AI tool.&lt;/strong&gt; You generated a UI with an AI assistant and want to refine it visually. See &lt;a href="https://crafttor.com/blog/ai-generated-ui-to-figma" rel="noopener noreferrer"&gt;AI generated UI to Figma&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Porting a UI.&lt;/strong&gt; You are moving a screen to a new framework and want a clean, measurable reference.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Figma basics you need for this
&lt;/h2&gt;

&lt;p&gt;You do not need to be a designer. Three Figma concepts cover most of it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frames&lt;/strong&gt; are containers, like a div.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Auto layout&lt;/strong&gt; is Figma's flexbox. A frame stacks children in a row or column with a gap and padding.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Text layers&lt;/strong&gt; hold real text with a font, size, weight, and line height you can read.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Click a layer and the right panel shows its values. Hold Option on Mac or Alt on Windows and hover over another layer to see the distance between them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step-by-step: from screenshot to measurable reference
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Capture the screen&lt;/strong&gt; at 1x to 2x of its real size. Browser screenshots at normal zoom work well.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open Figma&lt;/strong&gt;, create a file, and run Image to Figma Design. It works on the free Starter plan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign in&lt;/strong&gt; with a free Crafttor account.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paste the image&lt;/strong&gt; with Cmd+V or Ctrl+V.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick Turbo AI&lt;/strong&gt; if you care about structure. It costs 2 credits and rebuilds the screen as nested auto-layout frames, which map naturally to flex layouts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick Fast&lt;/strong&gt; if you only need text and positions. It costs 1 credit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inspect&lt;/strong&gt; frames, gaps, padding, font sizes, and colors.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Reading auto layout like CSS
&lt;/h2&gt;

&lt;p&gt;A Turbo AI conversion gives you nested frames. Each one roughly maps to a flex container:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Direction horizontal or vertical maps to flex-direction row or column.&lt;/li&gt;
&lt;li&gt;Gap maps to gap.&lt;/li&gt;
&lt;li&gt;Padding maps to padding.&lt;/li&gt;
&lt;li&gt;Alignment settings map to justify-content and align-items.&lt;/li&gt;
&lt;li&gt;Fill container and hug contents relate to flex-grow and fit-content sizing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This makes it easy to translate the screen into components. Treat the converted values as close estimates, not specs. They come from pixels, so round them to your spacing scale. Our &lt;a href="https://crafttor.com/blog/figma-auto-layout-from-image" rel="noopener noreferrer"&gt;figma auto layout from image&lt;/a&gt; guide explains the structure in more detail.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting HTML instead of layers
&lt;/h2&gt;

&lt;p&gt;Sometimes you want code, not a design file. The plugin can output a downloadable HTML file instead of placing layers on the canvas. That is useful for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A quick static prototype to share with a stakeholder.&lt;/li&gt;
&lt;li&gt;A starting point you refactor into your own components.&lt;/li&gt;
&lt;li&gt;A visual reference you open next to your editor.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Treat generated HTML as a first draft. A screenshot does not contain breakpoints, interactions, or data bindings. You will add those yourself. For tips on adapting the output to different widths, read &lt;a href="https://crafttor.com/blog/screenshot-to-responsive-html" rel="noopener noreferrer"&gt;screenshot to responsive HTML&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tips for better results
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Crop to the UI.&lt;/strong&gt; Leave out your IDE, terminal, and browser tabs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use real-looking data.&lt;/strong&gt; Lorem ipsum hides line-length problems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Capture one state per image.&lt;/strong&gt; Open menus, errors, and loading states each need their own capture.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid tiny screenshots.&lt;/strong&gt; Low resolution and blur reduce text accuracy. So do heavy gradients and busy illustrations.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where this fits next to other tools
&lt;/h2&gt;

&lt;p&gt;If you can open the live page in a browser, a page-capture tool such as html.to.design is another route, because it reads the rendered page. If you only have an image, a screenshot converter is the practical option. Figma also offers its own screenshot-to-design agent in open beta on paid plans. Choose based on what you have: a URL, an image, or a Figma plan.&lt;/p&gt;

&lt;p&gt;Only convert interfaces you own or have permission to use. When studying another product, rebuild for learning and do not ship copies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it in your next sprint
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.figma.com/community/plugin/1417763374654877658?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=screenshot-to-figma-for-developers" rel="noopener noreferrer"&gt;Install Image to Figma Design&lt;/a&gt; and convert the next screen you need to build. Logged-in users get free daily credits, so you can try it on a real ticket today.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Do I need design experience to use this?
&lt;/h3&gt;

&lt;p&gt;No. You paste a screenshot and get editable layers. Knowing frames, auto layout, and text layers is enough to inspect the result.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I get code instead of a Figma design?
&lt;/h3&gt;

&lt;p&gt;Yes. The plugin can output a downloadable HTML file. Treat it as a starting point and add breakpoints and logic yourself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Are the measurements exact?
&lt;/h3&gt;

&lt;p&gt;They are close estimates read from pixels. Round them to your spacing scale and confirm critical values against the live UI.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does it work on the free Figma plan?
&lt;/h3&gt;

&lt;p&gt;Yes. It works on every Figma plan, including the free Starter plan. You sign in with a free Crafttor account.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which mode is closest to how I write layouts?
&lt;/h3&gt;

&lt;p&gt;Turbo AI, because it produces nested auto-layout frames that map to flex containers.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>webdev</category>
      <category>design</category>
      <category>html</category>
    </item>
    <item>
      <title>PSD to Figma: Import Photoshop Files as Editable Layers</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Sat, 31 Oct 2026 05:52:01 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/psd-to-figma-import-photoshop-files-as-editable-layers-8i4</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/psd-to-figma-import-photoshop-files-as-editable-layers-8i4</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmmaddw1gt0ig1dtjbok3.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmmaddw1gt0ig1dtjbok3.jpg" alt="Flat is over: a flattened PSD card splitting into editable layers" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Most "PSD to Figma" tools give you a picture. You import a mockup, and every button, headline and shadow is frozen into one image. Then you rebuild it by hand, pixel by pixel, guessing the font and eyedropping the colours.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;PSD to Figma&lt;/strong&gt; takes the other road. It reads the Photoshop file itself, layer by layer, and rebuilds it as native Figma nodes. Text stays text. Shapes stay shapes. Groups stay groups. Masks and layer styles come along for the ride.&lt;/p&gt;

&lt;h2&gt;
  
  
  What comes through as editable
&lt;/h2&gt;

&lt;p&gt;Drop a &lt;code&gt;.psd&lt;/code&gt; or &lt;code&gt;.psb&lt;/code&gt; on the plugin and you get:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Live text&lt;/strong&gt;: font, size, weight, line height and colour. If the font isn't in Figma, the text falls back to Inter and the plugin names the missing font.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vector shapes&lt;/strong&gt;: rectangles, ellipses and paths, with fills, strokes and gradients.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Masks&lt;/strong&gt;: vector masks and clipping masks, recreated as Figma masks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Layer effects&lt;/strong&gt;: drop and inner shadows, glows, strokes, colour and gradient overlays.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Groups as frames&lt;/strong&gt;: names, opacity, blend modes and visibility preserved.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repeated smart objects&lt;/strong&gt; become one component with instances.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Anything Figma has no equivalent for (Bevel &amp;amp; Emboss, warped text, adjustment layers) is baked as an image &lt;strong&gt;and listed in the import report&lt;/strong&gt;, so nothing fails silently.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqyeayot8wr01gic14i1l.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqyeayot8wr01gic14i1l.jpg" alt="What converts to editable layers" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Pick how deep to go
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Fully editable&lt;/strong&gt;: text, shapes, masks, gradients and styles as native layers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Editable text&lt;/strong&gt;: live text, everything else as crisp images.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Layers as images&lt;/strong&gt;: each layer as its own image, structure kept.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flattened&lt;/strong&gt;: one image of the whole file.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Batch import works too: drop ten PSDs at once and each becomes its own page.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq6poutlvgux1lmt9r59h.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq6poutlvgux1lmt9r59h.jpg" alt="Four import modes" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  It goes both ways
&lt;/h2&gt;

&lt;p&gt;Select frames in Figma and export them as a PSD: editable (real text layers and groups), layers, or flattened, at 1x, 2x or 3x. The file opens in Photoshop as a Photoshop file, not a screenshot.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl6h31xp9rqkgwafhmr0x.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl6h31xp9rqkgwafhmr0x.jpg" alt="Both ways" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Under the hood (for the curious)
&lt;/h2&gt;

&lt;p&gt;The parser runs in the plugin's UI iframe, so the whole PSD is read client-side with no upload. Figma's main thread then rebuilds nodes from an intermediate layer tree. Two limits worth knowing if you build Figma plugins: &lt;code&gt;figma.createImage&lt;/code&gt; rejects bitmaps wider or taller than 4096 px, so oversized raster layers are downscaled before being handed over, and text is placed by aligning the text box to the ink bounds of the original so baselines land where Photoshop drew them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where your files go
&lt;/h2&gt;

&lt;p&gt;The PSD is parsed on your machine, inside Figma. The plugin talks to Crafttor only for your account and credits, and sends limited usage details (the action, its mode, the file or frame name and size). Your artwork is never uploaded.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on a real file
&lt;/h2&gt;

&lt;p&gt;Drop the PSD, watch the preview, then sign in when you want to import. A free Crafttor account comes with free credits; paid plans refill credits every month.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkbct7tk8fdxsbmmxzmvy.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkbct7tk8fdxsbmmxzmvy.jpg" alt="Drop. Preview. Import." width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.figma.com/community/plugin/1687850435434962649" rel="noopener noreferrer"&gt;Install PSD to Figma on Figma Community&lt;/a&gt;&lt;/strong&gt; · Original post: &lt;a href="https://crafttor.com/blog/psd-to-figma" rel="noopener noreferrer"&gt;crafttor.com/blog/psd-to-figma&lt;/a&gt;&lt;/p&gt;

</description>
      <category>figma</category>
      <category>photoshop</category>
      <category>design</category>
      <category>tools</category>
    </item>
    <item>
      <title>Screenshot to Figma AI: How AI Rebuilds Screens as Layers</title>
      <dc:creator>Sandeep Virk</dc:creator>
      <pubDate>Fri, 30 Oct 2026 17:48:18 +0000</pubDate>
      <link>https://dev.to/sandeep_virk_31621a43cb7c/screenshot-to-figma-ai-how-ai-rebuilds-screens-as-layers-3186</link>
      <guid>https://dev.to/sandeep_virk_31621a43cb7c/screenshot-to-figma-ai-how-ai-rebuilds-screens-as-layers-3186</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://crafttor.com/blog/screenshot-to-figma-ai" rel="noopener noreferrer"&gt;Crafttor&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Plenty of tools now promise screenshot to Figma AI conversion. The phrase covers very different approaches, and the difference shows up the moment you try to edit the result. This post explains what AI adds compared with classic detection, where it helps most, and where you should still expect to step in.&lt;/p&gt;

&lt;p&gt;We will compare the two modes in Image to Figma Design. Fast uses classic computer vision. Turbo AI rebuilds the screen as nested auto layout frames.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two ways to read a screenshot
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Classic computer vision
&lt;/h3&gt;

&lt;p&gt;Classic detection looks for edges, color regions and text. It finds a rectangle with a fill, a block of text, an icon. It then places each item at the position where it appeared.&lt;/p&gt;

&lt;p&gt;This is fast and predictable. The result looks right. But the layers are mostly positioned in absolute coordinates. If you change a heading so it wraps to two lines, the text below does not move down.&lt;/p&gt;

&lt;h3&gt;
  
  
  AI structure reconstruction
&lt;/h3&gt;

&lt;p&gt;An AI approach tries to understand the screen the way a designer would. It asks questions like: which elements form a card? Which cards form a list? Is this row of buttons a horizontal group with even spacing?&lt;/p&gt;

&lt;p&gt;The answer becomes a tree of nested frames. In Image to Figma Design's Turbo AI mode, those frames use auto layout. Sections grow, shrink and ungroup cleanly because they are built from structure, not just coordinates.&lt;/p&gt;

&lt;h2&gt;
  
  
  What AI changes in your daily work
&lt;/h2&gt;

&lt;p&gt;The value of AI structure is not that the result looks better at first glance. Both modes can look close to the original. The value appears when you start editing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Content changes.&lt;/strong&gt; Make a card title longer and the card grows. Add a fourth feature to a three-column row and the row adapts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Resizing.&lt;/strong&gt; Stretch the page frame wider and sections with fill settings stretch with it. This is the base for a responsive layout.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reorganizing.&lt;/strong&gt; Drag a card out of a list and the remaining cards close the gap.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Handoff.&lt;/strong&gt; Developers can read auto layout as something close to flexbox. Padding and gaps are explicit values, not guesses.&lt;/p&gt;

&lt;h2&gt;
  
  
  When classic detection is the smarter choice
&lt;/h2&gt;

&lt;p&gt;AI is not always the right tool. Fast mode wins in several real cases:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You only need text pulled out of an image.&lt;/li&gt;
&lt;li&gt;You want a measured reference to trace over.&lt;/li&gt;
&lt;li&gt;The screen is a one-off you will discard after a review.&lt;/li&gt;
&lt;li&gt;You are converting a large batch and only a few screens need structure.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Fast costs 1 credit per conversion and returns the quickest result. Turbo AI costs 2 credits. Choosing well per screen is how you keep both quality and cost in check.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to run an AI screenshot to Figma conversion
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Install the plugin.&lt;/strong&gt; Get &lt;a href="https://www.figma.com/community/plugin/1417763374654877658?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=screenshot-to-figma-ai" rel="noopener noreferrer"&gt;Image to Figma Design&lt;/a&gt; from the Figma Community.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start it&lt;/strong&gt; from the Plugins menu in any file, on any Figma plan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign in&lt;/strong&gt; with a free Crafttor account.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add a screenshot&lt;/strong&gt; in PNG, JPEG or WEBP. Drag, browse or paste.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Select Turbo AI.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Convert.&lt;/strong&gt; The plugin places a frame tree with auto layout on the canvas.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test the structure.&lt;/strong&gt; Change a heading, resize the frame, and check how sections respond.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How to check AI output quality
&lt;/h2&gt;

&lt;p&gt;Do not judge the result only by how it looks at its original size. Run these quick tests:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The wrap test.&lt;/strong&gt; Make one heading twice as long. Does the content below move down?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The width test.&lt;/strong&gt; Resize the top frame wider. Do sections stretch or stay fixed as you would expect?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The removal test.&lt;/strong&gt; Delete one item from a list. Does the list close the gap?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The naming test.&lt;/strong&gt; Do the top-level frames match the real sections of the screen?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If most tests pass, you have a working layout. If one section fails, you can fix just that frame rather than rebuild everything. For more detail on what good structure looks like, read our &lt;a href="https://crafttor.com/blog/figma-auto-layout-from-image" rel="noopener noreferrer"&gt;auto layout from image guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where AI still needs your help
&lt;/h2&gt;

&lt;p&gt;AI structure is a strong starting point, not a finished file. Expect to step in on these:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Very busy illustrations&lt;/strong&gt; are hard to break into meaningful shapes. They often work best as a single image layer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Heavy gradients and blurred glass effects&lt;/strong&gt; are difficult to rebuild exactly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low-resolution or blurry screenshots&lt;/strong&gt; reduce accuracy for both text and structure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Design system mapping.&lt;/strong&gt; The AI does not know your components. Swap converted buttons and inputs for your library versions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Naming.&lt;/strong&gt; Rename frames so teammates can find things.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Other AI options in the market
&lt;/h2&gt;

&lt;p&gt;Figma now offers its own screenshot-to-design agent, in open beta on paid Figma plans. Tools such as Codia and image.to.design also offer AI conversion. Each has different trade-offs on plan requirements, output and workflow. Our &lt;a href="https://crafttor.com/blog/best-figma-plugins-image-to-design" rel="noopener noreferrer"&gt;roundup of image to design plugins&lt;/a&gt; compares them fairly.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick word on permission
&lt;/h2&gt;

&lt;p&gt;Use AI conversion on screens you own or have permission to use. For inspiration, rebuild for study and do not ship copies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try AI conversion on one screen
&lt;/h2&gt;

&lt;p&gt;Pick a screen you know you will edit later and run it in Turbo AI. Then run the four tests above. &lt;a href="https://www.figma.com/community/plugin/1417763374654877658?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=screenshot-to-figma-ai" rel="noopener noreferrer"&gt;Install Image to Figma Design&lt;/a&gt; and use your free daily credits to see the structure for yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is the difference between AI and regular screenshot conversion?
&lt;/h3&gt;

&lt;p&gt;Regular conversion places detected shapes and text at fixed positions. AI conversion groups them into nested frames that understand sections, lists and rows.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Turbo AI use auto layout?
&lt;/h3&gt;

&lt;p&gt;Yes. Turbo AI rebuilds the screen as nested auto layout frames, so sections resize and ungroup cleanly.&lt;/p&gt;

&lt;h3&gt;
  
  
  How many credits does AI conversion cost?
&lt;/h3&gt;

&lt;p&gt;Turbo AI uses 2 credits per conversion. Fast mode uses 1 credit.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will AI conversion match my design system?
&lt;/h3&gt;

&lt;p&gt;It creates generic frames, shapes and text. You can then replace buttons, inputs and cards with components from your own library.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is the AI result always better than Fast?
&lt;/h3&gt;

&lt;p&gt;Not always. For quick references, text extraction or throwaway screens, Fast is cheaper and quicker. Use Turbo AI when you will keep editing.&lt;/p&gt;

</description>
      <category>figma</category>
      <category>ai</category>
      <category>design</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
