Design · Term

Wireframe

A wireframe is a low-fidelity layout of a screen that shows structure and hierarchy — where things go — without final visual design.

Wireframes are a thinking tool: they let a team agree on structure and flow before investing in polished visuals. They sit early in the path from idea to shipped product, keeping decisions cheap while they are still easy to change.

How it works

A wireframe uses boxes, lines and placeholder or real draft text to show what goes on a screen and in what order: navigation, headings, content blocks, forms and calls to action. Colour, imagery and final typography are deliberately left out, so feedback stays on structure, priority and flow rather than taste.

A set of wireframes linked together becomes a clickable prototype for testing a flow.

Example

Before designing a service page, a wireframe can settle the order of the answer, the proof, the price signal and the call to action. Moving the proof above the fold at this stage takes a minute; doing it after the page is designed and built takes a day.

In practice

When a designer sends wireframes for review, check each page against three questions: does it answer what a customer arriving here wants to know, in the order they want to know it; is the next step obvious; and is anything important missing, such as prices, areas served, opening hours or proof like reviews and examples of work. Comment on structure and content, not on fonts or colours, which are not decided yet. If you find yourself unable to judge a page, ask for it with real draft text.

Ask to see the mobile wireframes alongside the desktop ones, since many visitors to a small business site arrive on phones, and the order of content on a narrow screen can differ from the desktop layout. Check how the information architecture works across pages: whether the menu labels match what customers call your services, and whether every key page can be reached in a couple of taps. Agree in writing when wireframes are approved, because later structural changes usually mean redesign work. A short sign-off email protects both sides from expensive surprises.

Why it matters for your business

Wireframe review is the cheapest moment in a website project to change your mind, and it is where owners have the most useful say. Decisions made here, such as what sits above the fold, where the call to action goes, and which questions each page answers first, shape enquiries far more than colour choices later. Because wireframes look plain, it is tempting to skim them and wait for the polished design. That postpones the important decisions to a stage where every change costs more. Give wireframes the same attention as a final design, check them against what customers actually ask, and approve structure before visuals.

Common mistakes

  • Using lorem ipsum everywhere, which hides whether the real content fits.
  • Adding visual polish too early, so reviewers debate colours instead of structure.
  • Skipping mobile wireframes and discovering the layout problems in development.

Questions people ask

What is the difference between a wireframe and a mockup?

A wireframe shows structure: what goes on a screen and in what order, using plain boxes and draft text. A mockup shows the final look of that screen, with real colours, typography and images, but still nothing to click. Wireframes come first so structure is settled before anyone discusses visual style.

What tools are used to create wireframes?

Anything from paper and a whiteboard to dedicated design software. Many teams use Figma or a similar tool, which lets wireframes be shared, commented on and later linked into a clickable prototype. The tool matters less than the content: real headings, real draft copy and a clear order for each page.

Do I need wireframes for a small website?

Usually yes, even if they are quick sketches. A few wireframes for the home page and a typical service page settle what each page must say and where the contact options go, which avoids costly changes later. The main exception is a site built on a proven template where the structure is already decided.

Read: How to prototype an interaction before you build it →

Related terms

Have something worth building right?