What a reference map is and why you need one
A reference map is a visual collection you build yourself—images, color palettes, layouts, typography choices, and design details you want to remember and use later. Instead of scrolling through thousands of bookmarks or screenshots when you start a project, you have one organized place where your visual ideas live.
The difference between a reference map and a random folder of screenshots is organization. A reference map groups images by what they teach you: color combinations that work together, how other designers handle white space, the way certain fonts pair, how shadows fall in product photography. When you sit down to design something, you can pull from your map and see patterns in your own taste instead of starting blank.
You build this map as you work and browse. Every time you see a design choice that makes you stop and look—a website layout, a poster, a photograph, a color scheme—you save it with a note about why it caught your attention. Over months, the map becomes a visual record of what you actually like, not what you think you should like.
Key Takeaways
- A reference map is an organized collection of images and design details you build over time, grouped by what they teach you rather than stored randomly.
- The best reference maps live in tools you already use daily—a Pinterest board, a shared folder, a Figma file, or a straightforward spreadsheet with image links—so you actually add to them.
- Tag or label each image with what caught your eye: the color palette, the typeface pairing, the composition, or the specific problem it solves.
- Review your map before starting a new project to see patterns in your own taste and avoid repeating the same choices unconsciously.
- A reference map works best when it stays small and focused—fifty images you actually use beats five hundred you never look at again.
Choose a tool that fits how you actually work
The tool matters less than whether you will use it. A reference map in a tool you check every day beats a perfect system you abandon after two weeks.
If you design in Figma, create a file called "Reference" with pages for each category: color, typography, layout, photography style, UI patterns. Paste images directly into the file. You can add text notes next to each one. Because the file lives where you work, you will see it and add to it naturally. Figma also lets you share the file with collaborators, so a team can build the map together.
If you work in Adobe Creative Suite, a shared folder on your computer or cloud storage works well. Create subfolders: "Color Palettes," "Typography," "Layouts," "Photography." Save images as files or screenshots. You can open the folder while you work in Photoshop or Illustrator and drag images into your canvas to study them. Add a straightforward text file in each folder describing what each image shows.
Pinterest works if you are comfortable with a public or private board. Create a board for your reference map and pin images as you find them. The search function lets you find images later by keyword. The downside: Pinterest's algorithm will suggest related pins, which can distract you from your actual map. Use it only if you have the discipline to stay focused.
A Google Sheet or Airtable works if you want to add detailed notes. Create columns: Image (paste a screenshot or link), Category, What I Noticed, Project It Might Fit, Date Added. This approach takes more time to maintain but gives you a searchable database. Airtable lets you attach images directly and filter by tag, which is powerful if your map grows large.
A straightforward folder on your computer with organized subfolders is the fastest to start. No login, no learning a new tool, no sync delays. The trade-off: you have to open the folder manually, and searching takes longer. This works well if you are just starting and want to see whether you will actually use a reference map before investing time in a fancier system.
What to collect and how to label it
Collect images that make you stop. Not images that are technically perfect or award-winning—images that make you curious about why they work. A photograph with interesting shadow play. A website where the navigation feels obvious. A color palette that feels calm. A typeface pairing that looks modern without trying too hard.
When you save an image, add a label that describes what you learned from it, not just what it is. Instead of "website design," write "navigation stays visible while scrolling" or "white space between sections makes content feel less crowded." Instead of "photo," write "soft backlight creates rim light on hair" or "muted colors with one bright accent." These notes are for future you, who will have forgotten why you saved it.
Organize by what the image teaches, not by where it came from. Group by: Color Palettes, Typography Pairings, Layout Patterns, Photography Lighting, UI Components, Composition, Texture and Pattern, Negative Space. These categories work across mediums. A photograph that uses negative space well teaches the same lesson as a poster that does.
Add the date you saved it. In six months, you will want to know whether an image is recent or from years ago, because design trends shift. Recent images keep your map current.
How to use your reference map when you start a project
Before you open a blank canvas, spend ten minutes with your reference map. Look at images in the category that matches your project. If you are designing a poster, look at your layout and composition images. If you are photographing a product, look at your lighting and color images. Do not try to copy any single image. Instead, notice what appears in multiple images. That pattern is probably something your eye naturally gravitates toward.
Pull three to five images that feel closest to the mood you want. Keep them visible while you work—in a second monitor, a printed sheet, or a window next to your design software. Refer back to them when you get stuck. Do not copy them directly. Use them to answer specific questions: "How much white space should this have?" or "What happens if I use this color combination?" or "How does this photographer handle shadows?"
After you finish the project, add it to your reference map if it turned out well. Your own finished work becomes part of what you learn from. Over time, your map will include images from other designers and photographers mixed with your own work, creating a visual record of your growth.
Keep your map focused and actually use it
A reference map with five hundred images you never look at is worse than useless—it creates the illusion that you have a system when you do not. A map with fifty images you actually study is powerful.
Every few months, review your map and delete images that no longer speak to you. If you saved something six months ago and have never opened it, remove it. Your taste changes. An image that felt exciting last year might feel dated now. Let it go. The map should reflect what you actually like right now, not a historical record of every image you ever found interesting.
Add to your map regularly as you work and browse. When you see something that stops you, save it when ready. Do not tell yourself you will add it later—you will forget. Make it a habit: see something interesting, add it to the map with a note, move on. Five minutes a week of adding images beats an hour once a month of trying to catch up.
Share your map with other designers or photographers you work with. A team reference map keeps everyone aligned on visual direction without needing long conversations about style. When someone asks "what kind of color palette are we going for?" you can point to the map instead of describing it.
Common mistakes that kill a reference map
Saving images without labels is the fastest way to make your map useless. Six months later, you will have a folder of beautiful images and no memory of why you saved any of them. Always write a one-sentence note about what caught your eye.
Organizing by source instead of by lesson wastes time. A folder called "Websites I Like" mixes images that teach different things. You end up scrolling through dozens of images to find one that shows how to use color, when you could have a dedicated color folder with ten images that all teach that one thing.
Letting your map grow without limit turns it into a junk drawer. You will stop looking at it because finding anything takes too long. Delete regularly. A small, focused map you actually use beats a massive archive you ignore.
Treating your map as a place to save everything you find instead of a place to save things you will actually use. Be selective. If an image is technically interesting but does not match your taste or your work, do not save it. Your map should be a reflection of what you actually make, not a museum of design history.
Frequently Asked Questions
Should I organize my reference map by project or by design element?
Organize by design element—color, typography, layout, photography style. A project-based map forces you to look through old projects to find relevant images. An element-based map lets you pull from across all your past work and inspiration, which is how you actually build new things. You combine elements from different sources, not copy entire projects.
What if I find an image I love but do not know why?
Save it anyway, but write "not sure yet" in the label. As you build your map, patterns will emerge. You might notice that all your favorite images use a certain color range, or have a lot of white space, or use the same typeface family. Those patterns tell you what your eye actually responds to, even if you could not articulate it at first.
Can I use my reference map for client work or does it have to be personal?
Use it for both. A reference map for a specific client project—images that match their brand direction, their industry, their audience—keeps the team focused and speeds up feedback. A personal map of your own taste helps you develop a consistent visual voice across all your work. Many designers keep both: a general map of their taste and project-specific maps for bigger jobs.
How often should I review and update my reference map?
Add images as you find them, and review the whole map every three to six months. Delete images that no longer feel relevant. Add new categories if you notice you are collecting images that do not fit anywhere. The map should evolve as your work and taste evolve. A map that stays exactly the same for a year is probably not being used.
Should my reference map be private or can I share it?
Share it with your team or collaborators if you work with others. A shared map keeps everyone aligned on visual direction and saves time in feedback meetings. Keep it private if it is personal work or if you are worried about your taste being copied. Many designers keep both: a private map for exploration and a shared map for client work.