Skip to content

Guide

Image to HTML

A screenshot is the least information a conversion can start from — here is what tools can genuinely do with one, and what still has to be decided by a person.

Sometimes an image is all that exists. The agency that built the site has gone, the source files went with them, and what you have is a JPG, a PDF export or a screenshot. That is a workable starting point — it is simply the hardest one, and it helps to know why before choosing how to handle it.

An image carries no structure whatsoever. A PSD at least has named layers with coordinates and a Figma file has explicit layout rules, but a flat image is a grid of pixels. Every single thing a converter needs — where one element ends and the next begins, which text is a heading, what the exact hex value is under compression, how much padding is intentional — has to be inferred from appearance alone.

Vision models have become genuinely good at that inference, and this is the area where AI changed the picture most. Give a current model a screenshot and it will identify the regions, read the text accurately in most cases, approximate the colours closely, and produce clean, modern, readable CSS. Five years ago this did not work at all. It is worth being clear that this part is now impressive.

What it cannot do is recover information the image never contained. Text rendered at 15.8px after JPEG compression might be 15px or 16px, and the model picks one. A colour sampled from a compressed screenshot is near your brand value but not equal to it. Anything below the fold does not exist. Hover and focus states do not exist. And the responsive behaviour, again, was never in the file — so any breakpoints in the output are invented.

The compounding problem is that these small inventions are individually invisible and collectively obvious. A spacing scale that is 15, 23, 31 and 46 pixels instead of 16, 24, 32 and 48 looks fine in isolation and looks subtly wrong as a page — and it is unusable as a system, because nothing lines up with anything. Cleaning that up afterwards is slower than measuring it correctly once.

So the way we work from images is to treat the generated pass as a draft and the measurement as the actual job. A developer establishes the real scale — the grid, the type ramp, the spacing steps, the true brand colours if you can tell us them — and builds against that. Where the image genuinely does not say, we ask you rather than guess, and we list every assumption we made in the handover so nothing is silently invented.

That is the same arrangement described on our AI-assisted development page, and it is why we can take screenshot work at a sensible price rather than pricing it as forensic reconstruction. If you do have a layered source file, say so — a PSD converts better than a flat export, and a Figma file better still.

How much your source file actually carries
Source What the file contains What has to be inferred
Figma with auto-layout Layout rules, variables, components, constraints Very little — behaviour between breakpoints
PSD or layered file Named layers, coordinates, exact colours, live text Grouping, semantics, all responsive behaviour
PDF or vector export Vector shapes and selectable text All structure and layout intent
JPG, PNG or screenshot Pixels Everything — measurements, colours, structure, states

What we can work from

  • Screenshots of a live site, ideally full-page and at 2x where you can
  • JPG or PNG exports of a design, at the largest size you have
  • PDF exports — better than raster, because text and vectors stay measurable
  • A photograph of a printed layout, for genuine reconstruction jobs
  • Any brand values you can supply — hex codes, font names, a style guide
  • A note on what should happen on mobile, if you have a view on it

Send whatever you have. We will tell you what can be read from it reliably, what will need a decision from you, and what it costs — before you commit to anything.

Want it done properly? PSD to HTML5 from $49

Hand-coded, responsive, W3C validated and accessible — with a fixed quote before you commit.

See PSD to HTML5 Ask a question
  • Image to HTML
  • Screenshot to Code
  • JPG to HTML
  • AI-Assisted
  • Responsive
  • Accessible
  • Image to HTML
  • Screenshot to Code
  • JPG to HTML
  • AI-Assisted
  • Responsive
  • Accessible

FAQ

Image to HTML — questions we get asked

Can AI convert an image to HTML?
Yes, and reasonably well for a first draft. A current vision model reads the text, identifies the regions and writes clean CSS. It also invents the exact measurements, the colours under compression and all responsive behaviour, because none of that is recoverable from a flat image.
Is there a free image to HTML converter?
Several AI tools will do it in a browser at no cost, and they are worth trying to see what you get. Judge the output on structure rather than appearance: check whether buttons are real buttons, whether headings are headings, and what happens when you narrow the window.
What resolution should I send?
The largest you have — 2x is ideal. Compression artefacts are the main thing that makes colours and edges ambiguous, so an original PNG beats a re-saved JPG, and a full-page capture beats a cropped one.
Will the result be pixel perfect?
It will match the image closely, and we will tell you where the image was genuinely ambiguous rather than pretending otherwise. If you can supply the brand hex codes and font names, accuracy goes up considerably at no extra cost.

A friendly team who create neat stuff for our clients

Tell us about your project and we will get back to you with a fixed price and a delivery date.