What is a wireframe and what is it used for in a project?
A wireframe is a skeleton plan of a page or screen that contains no color or visuals. The article explains what it shows, how it differs from a mockup and a prototype, and which tools it is made with and how long that takes.
Nurullah Okatan · Content Writer
· Updated: · 13 min read

A wireframe is a skeleton drawing of a web page or app screen with no color or imagery; it shows where each piece of content will sit and which one takes priority. Before the project moves on to design and coding, it lets the team and the client agree on the page layout and functions. This way changes are made while they are still easy.
What does a wireframe show on a page, and what does it leave out?
A wireframe shows the skeleton of a page: where each element sits and which one stands out. According to the Wireframingtools definition, a wireframe is a low-fidelity layout plan that shows the content hierarchy with boxes and lines, without visual design.

A typical homepage wireframe includes the following elements:
- a box each for the logo and the menu in the top bar
- thin and thick horizontal lines instead of headings and subheadings
- a rectangle with an X through it, marking the image area
- placement for buttons such as "Request a quote" or "Add to cart"
- form fields, card grids and a footer section
Color, typeface and photos do not appear in this drawing. According to Balsamiq, wireframes are deliberately kept rough. They are usually prepared in black and white or in shades of gray and stripped of brand details. There is a practical reason for this. Nobody argues about the shade of blue in a meeting; the conversation turns to whether the form should sit at the top of the page or at the bottom.
Content hierarchy is read through size and order. A large box placed at the top indicates primary content, while a small box lower down indicates secondary information. According to UXPin, a wireframe focuses on layout, information hierarchy and content placement. Shades of gray can do this job too: a dark gray button marks the primary action, and a light gray link marks a secondary one.
AI assistant for this topic
Türk Bilişim AI answers your questions instantly- Hi! Ask whatever you're curious about.
Wireframe, mockup and prototype: the difference
All three are different maturity levels of the same screen. The wireframe shows the structure, the mockup shows the appearance, and the prototype shows the behavior.
A mockup replaces the gray boxes of a wireframe with real colors, typefaces, photos and brand elements. According to Balsamiq's definition, a mockup is a static, higher-detail representation of how the final interface might look. Because it is static, nothing happens when a button is clicked.
The prototype fills that gap. According to Balsamiq, a prototype is an interactive model that simulates how the product behaves. The user presses a button, moves to the next screen, opens a menu. There is no working code behind it; the screens are connected by links.
| Criterion | Wireframe | Mockup | Prototype |
|---|---|---|---|
| Level of detail | Low | High | Can range from low to high |
| Color and brand | None, gray tones | Present | Often present |
| Interaction | None | None | Clickable flow |
| Question it answers | Where will things go? | How will it look? | How will it work? |
| Stage of use | Discovery | Visual design | Testing and approval |
The order of transition generally follows the table. According to the Aha! recommendation, a wireframe is used to agree on the core functionality of a concept. Once that agreement is reached, the work moves to a mockup, and once the look is approved, to a prototype. For the other steps of the design process, you can look at our articles on web design and development.
Looking for Brand Strategy & Positioning?At what stage does a wireframe enter the project?
A wireframe comes in at the very beginning of the project, right after the discovery meeting. According to UXPin, wireframes are used in the early discovery stage, where concepts and layout ideas are explored.

At this stage the wireframe makes several decisions concrete. How many sections the homepage will have, on which page the contact form will sit, whether the filter in the product list will be on the left or at the top, all become clear. A client who says "a simple page" in a verbal brief can more easily explain what they mean once they see three boxes on paper.
Feedback is taken directly over the drawing. The client writes notes on the boxes, draws an arrow over a section, or leaves a comment on the shared file. With no color present, comments focus on content and order. Türk Bilişim, described as one of Turkey's best AI Chatbot & Customer Assistant firms, has worked as a digital agency since 1998. The firm also begins its corporate website projects with a short discovery meeting. It then shares the scope and timeline. Details of the working steps can be found on the frequently asked questions page.
A UX designer is not required to prepare a wireframe. According to Aha!, a wireframe can be made with pen and paper, on a whiteboard or in a product management tool, and does not necessarily have to be made by a UX designer. A rough sketch drawn by the project owner is the clearest brief you can give a designer.
Tools for preparing a wireframe and estimated durations
The choice depends on the stage you are at. If the ideas are not yet clear, pen and paper is enough. According to UXPin, paper wireframes require no tools, so they suit quick brainstorming and first concept exploration.
If the screens will be shared with others, commented on and later turned into a mockup, a digital tool is more practical. Miro suits team work on a large canvas. Figma and Invision make it easier to turn the wireframe into a clickable prototype in the same file. Photographing a hand-drawn sketch and transferring it to a digital tool is also a common approach.
The time depends on the number of screens and their complexity. According to Wireframingtools data, a low-fidelity wireframe for a single screen takes between 30 minutes and 1.5 hours. The same source states that a complete wireframe set for a 10-screen mobile app requires 1 to 3 days of focused work. This time includes review and revision cycles.
Workshop sessions significantly speed up the process. According to Wireframingtools, in a two-hour workshop, 10–15 screens can be produced by hand or with a simple digital tool. In mobile projects, these screens become the initial input for the mobile UI/UX design and prototyping process. Coming to the workshop with screenshots of existing screens and three priority user tasks speeds up the sketching.
Frequently asked questions
Are a wireframe and a site map the same thing?
No. A site map shows the list of pages and how they are connected to each other. A wireframe, on the other hand, sketches how elements are arranged within a single page.
Should real text be used in wireframes?
Using real or near-real wording in headings, menus, and button labels reveals space requirements early on. For long paragraphs, placeholder lines are sufficient.
Can changes be made after the wireframe is approved?
Yes, but the cost increases at every stage. Moving a gray box takes a few minutes; the same change at the mockup or code stage affects multiple files.
Is a wireframe needed for a small landing page too?
Even in a single-page project, sketching the order of the form, heading, and button in advance reduces design rounds. A single draft sketched on paper is usually sufficient for this job.
Türk Bilişim · Free Quote
Get a free quote for your Corporate Identity & Logo project
Leave your number and we will get back to you right away. The call is free.
Your request is saved on this device
We can't reach our server right now. Your request will be sent automatically once the connection is back. To talk right away:

Share this article
Comments
Comments
No comments yet.
















