Give each image a job
A portfolio image may be immediately recognizable to you but puzzling to someone encountering the project for the first time. A caption closes that gap. It should help a visitor understand what the image shows and why you chose to include it. Before writing, decide what the image contributes to the story: Does it show an early exploration, a design decision, a working prototype, or the delivered result? If it does not add something distinct, consider removing it rather than writing a caption that repeats the project summary.
Start with a plain description, then add the relevant point. For example, “Early layout options for a community event page, comparing how prominently to display the date and location” tells readers both what they see and what the comparison was about. A label such as “Website design” gives them much less to work with. Keep the caption close to the image so readers do not have to guess which explanation belongs to which visual.
Use context without retelling the whole project
A useful caption often answers three questions: What is this? What should I notice? How does it fit into the project? You rarely need a full paragraph to answer all three. For a student project, you might write, “Paper sketches from the first navigation exercise; the final concept uses the simpler two-level menu shown on the right.” For freelance work, a caption might identify the client-approved deliverable and the specific feature visible in the image.
Let the project introduction carry the broader brief, audience and outcome. Captions can then focus on details that would otherwise be missed: a change between versions, a constraint that shaped the layout, or the reason you included a particular screen. Write for someone scanning the page as well as someone reading it closely. A clear first sentence should stand on its own; an optional second sentence can supply the decision behind it.
Make your contribution and the work’s status clear
Portfolio work is often collaborative. If an image contains work by several people, describe your part without implying you created everything shown. You could say, “I designed the icon set and page hierarchy; a teammate developed the interactive build.” Small teams can use the same approach for shared deliverables. This gives credit while making your skills easier to assess. If a supplied photo, template or brand asset appears in the image, avoid presenting that asset as your own creation.
Prototypes also need an honest status label. An interactive mockup, a clickable screen flow and a released product are different things. State whether viewers are seeing an exploration, a test version, a proposed design or a finished deliverable. For example: “Clickable checkout prototype used to review the order steps; payment processing was not built.” That detail prevents a polished demonstration from being mistaken for a fully functioning product.
Describe movement and comparisons precisely
A still image cannot always explain an interaction. For prototype screens, name the action and its visible response: “Selecting a filter updates the results list and leaves the active filter visible above it.” If the interaction is only proposed, say so. For a short video or animation, note the moment worth watching rather than writing “See video.” Visitors who cannot play it should still be able to understand the point you are making.
When showing before-and-after images, identify which is which and explain the meaningful change. “Before: event details sat below a large banner. After: the date, venue and booking link appear together at the top” is more useful than “Redesign.” Be careful with outcome claims: a clearer layout is a design intention or observation, not proof that more people completed a task. If you did not measure an effect, describe the change and its purpose instead.
Edit captions for clarity, consistency and access
Once the gallery is assembled, read the captions in sequence without looking at the images. They should form a coherent account of the work without repeating the same project background on every slide. Use consistent names for features and project stages. Replace vague praise such as “clean” or “intuitive” with observable details: what was simplified, grouped, removed or made more prominent. Trim any sentence that does not help readers interpret the visual or understand your role.
Captions and alternative text serve related but different purposes. A visible caption can explain a design decision; alternative text should convey the image’s essential visual information to someone who cannot see it. One does not automatically replace the other. Before publishing, also check that captions do not reveal private client information, unreleased details or names you do not have permission to share. The best caption is brief enough to scan and specific enough to make the image worth seeing.
