Urgent.News

What's breaking now, across thousands of outlets.

Tech

Screenshot to HTML: Turn Any UI Image Into Web Code

Originally published on Crafttor . Sometimes you do not need a design file at all. You need a page in a browser, fast. A screenshot to HTML conversion skips the hand coding of a first draft and gives you markup you can open, share and edit. This guide explains how the HTML export in Image to Figma Design works and what the file is good for. It also covers where you should still bring in a…

Crafttor released a plugin called Image to Figma Design that converts screenshots into HTML code. This allows users to quickly prototype web interfaces without needing a separate design file. The plugin offers two modes, Fast and Turbo AI, that determine how the HTML is generated. Fast uses traditional shape detection and text recognition while Turbo AI creates nested auto layout containers which tend to map more naturally to HTML structure.

To use the plugin, you first install it from the Figma Community. Then, open a Figma file and sign in with a Crafttor account. You can then drag in a PNG, JPEG or WEBP image, choose Fast or Turbo AI, and select HTML output. The plugin then generates an HTML file that can be reviewed and edited in a browser or code editor.

When reviewing the generated HTML, check for real selectable text, correct layout, images, and proper sizing. It's also important to ensure the layout holds up when resized. The HTML export is useful for quick prototypes, visual baselines for developers, recovering copy and layout from old screens, and learning markup structures.

However, it is not a replacement for production code as it lacks any behavior or accessibility details. Treat the export as a first draft and developers should still add interactivity, semantics and integrate it into your codebase. For best results, start with a sharp image, convert one section at a time, remove overlays and busy illustrations, and use Turbo AI for layouts you plan to keep.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

LiteLLM 1.107.0 compromise: incident response guide

What happened The LiteLLM 1.107.0 compromise began on October 21, 2026, when a compromised litellm==1.107.0 was published to PyPI and to LiteLLM's container registries. LiteLLM's incident post states that earlier versions are safe, that the affected releases were pulled, and that customers on the private enterprise release were not…

  • Compromised LiteLLM 1.107.0 released on PyPI and container registries
  • Attack chain lasted two hours, potentially accessing sensitive data
  • Response includes identifying and isolating affected packages

More from Friday 30 October →