loading . . . Itβs hard to justify Tahoe icons I was reading Macintosh Human Interface Guidelines from 1992 and found this nice illustration:
accompanied by explanation:
Fast forward to 2025. Apple releases macOS Tahoe. Main attraction? Adding unpleasant, distracting, illegible, messy, cluttered, confusing, frustrating icons (their words, not mine!) to every menu item:
Sequoia β Tahoe
Itβs bad. But why exactly is it bad? Letβs delve into it!
Disclaimer: screenshots are a mix from macOS 26.1 and 26.2, taken from stock Apple apps only that come pre-installed with the system. No system settings were modified.
# Icons should differentiate
The main function of an icon is to help you find what you are looking for faster.
Perhaps counter-intuitively, adding an icon to everything is exactly the wrong thing to do. To stand out, things need to be different. But if everything has an icon, nothing stands out.
The same applies to color: black-and-white icons look clean, but they donβt help you find things faster!
Microsoft used to know this:
Look how much faster you can find Save or Share in the right variant:
It also looks cleaner. Less cluttered.
A colored version would be even better (clearer separation of text from icon, faster to find):
I know you wonβt like how it looks. I donβt like it either. These icons are hard to work with. Youβll have to actually design for color to look nice. But the principle stands: it is way easier to use.
# Consistency between apps
If you want icons to work, they need to be _consistent_. I need to be able to learn what to look for.
For example, I see a βCutβ command and next to it. Okay, I think. Next time Iβm looking for βCut,β I might save some time and start looking for instead.
How is Tahoe doing on that front? I present to you: Fifty Shades of βNewβ:
I even collected them all together, so the absurdity of the situation is more obvious.
Granted, some of them are different operations, so they have different icons. I guess creating a smart folder is different from creating a journal entry. But this?
Or this:
Or this:
There is no excuse.
Same deal with open:
Save:
Yes. One of them is a checkmark. And they canβt even agree on the direction of an arrow!
Close:
Find (which is sometimes called Search, and sometimes Filter):
Delete (from Cut-Copy-Paste-Delete fame):
Minimize window.
These are not some obscure, unique operations. These are OS basics, these are foundational. Every app has them, and they are always in the same place. They shouldnβt look different!
# Consistency inside the same app
Icons are also used in toolbars. Conceptually, operations in a toolbar are identical to operations called through the menu, and thus should use the same icons. Thatβs the simplest case to implement: inside the same app, often on the same screen. How hard can it be to stay consistent?
Preview:
Photos: same and mismatch, but reversed Β―\\_(γ)_/Β―
Maps and others often use different symbols for zoom:
# Icon reuse
Another cardinal sin is to use the same icon for different actions. Imagine: I have learned that means βNewβ:
Then I open an app and see. βCoolβ, I think, βI already know what it meansβ:
Gotcha!
Youβd think: okay, means quick look:
Sometimes, sure. Some other times, means βShow completedβ:
Sometimes is βImportβ:
Sometimes is βUpdatesβ:
Same as with consistency, icon reuse doesnβt only happen between apps. Sometimes you see in a toolbar:
Then go to the menu _in the same app_ and see means something else:
Sometimes identical icons meet in the same menu.
Sometimes next to each other.
Sometimes they put an entire barrage of identical icons in a row:
This doesnβt help anyone. No user will find a menu item faster or will understand the function better if all icons are the same.
The worst case of icon reuse so far has been the Photos app:
It feels like the person tasked with choosing a unique icon for every menu item just ran out of ideas.
Understandable.
# Too much nuance
When looking at icons, we usually allow for slight differences in execution. That lets us, for example, understand that these _technically different_ road signs mean the same thing:
Same applies for icons: if you draw an arrow going out of the box in one place and also an arrow and the box but at a slightly different angle, or with different stroke width, or make one filled, we will understand them as meaning the same thing.
Like, is supposed to mean something else from ? Come on!
Or two-letter As that only slightly differ in the font size:
A pencil is βRenameβ but a slightly thicker pencil is βHighlightβ?
Arrows that use different diagonals?
Three dots occupying β
of space vs three dots occupying everything. Seriously?
Slightly darker dots?
The sheet of paper that changes meaning depending on if its corner is folded or if there are lines inside?
But the final boss are arrows. They are all different:
Supposedly, a user must become an expert at noticing how squished the circle is, if it starts top to right or bottom to right, and how far the arrowβs end goes.
Do I care? Honestly, no. I couldβve given it a shot, maybe, if Apple applied these consistently. But Apple considers and to mean the same thing in one place, and expects me to notice minute details like this in another?
Sorry, I canβt trust you. Not after everything Iβve seen.
# Detalization
Icons are supposed to be easily recognizable from a distance. Every icon designer knows: small details are no-go. You can have them sometimes, maybe, for aesthetic purposes, but you canβt _rely_ on them.
And icons in Tahoe menus are _tiny_. Most of them fit in a 12Γ12 pixel square (actual resolution is 24Γ24 because of Retina), and because many of them are not square, one dimension is usually even less than 12.
Itβs not a lot of space to work with! Even Windows 95 had 16Γ16 icons. If we take the typical DPI of that era at 72 dots per inch, we get a physical icon size of 0.22 inches (5.6 mm). On a modern MacBook Pro with 254 DPI, Tahoeβs 24Γ24 icons are 0.09 inches (2.4 mm). Sure, 24 is bigger than 16, but in reality, these iconsβ area is 4 times as small!
Simulated physical size comparison between 16Γ16 at 72 DPI (left) and 24Γ24 at 254 DPI (right)
So when I see this:
I struggle. I can tell they are different. But I definitely struggle to tell whatβs being drawn.
Even zoomed in 20Γ, itβs still a mess:
Or here. These are three different icons:
Am I supposed to tell plus sign from sparkle here?
Some of these lines are half the pixel thicker than the other lines, and thatβs supposed to be the main point:
Is this supposed to be an arrow?
A paintbrush?
Look, a tiny camera.
It even got an even tinier viewfinder, which you can almost see if you zoom in 20Γ:
Or here. There is a box, inside that box is a circle, and inside it is a tiny letter. `i` with a total height of 2 pixels:
Donβt see it?
I donβt. But itβs there...
And this is a window! It even has traffic lights! How adorable:
Remember: these are retina pixels, ΒΌ of a real pixel. Steve Jobs himself claimed they were invisible.
> It turns out thereβs a magic number right around 300 pixels per inch, that when you hold something around to 10 to 12 inches away from your eyes, is the limit of the human retina to differentiate the pixels.
And yet, Tahoe icons rely on you being able to see them.
# Pixel grid
When you have so little space to work with, every pixel matters. You can make a good icon, but you have to choose your pixels very carefully.
For Tahoe icons, Apple decided to use vector fonts instead of good old-fashioned bitmaps. It saves Apple resourcesβdraw once, use everywhere. Any size, any display resolution, any font width.
But thereβre downsides: fonts are hard to position vertically, their size doesnβt map directly to pixels, stroke width doesnβt map 1-to-1 to pixel grid, etc. So, they work everywhere, but they also look blurry and mediocre everywhere:
Tahoe icon (left) and its pixel-aligned version (right).
They certainly start to work better once you give them more pixels.
iPad OS 26 vs macOS 26
or make graphics simpler. But the combination of small details and tiny icon size is deadly. So, until Apple releases MacBooks with 380+ DPI, unfortunately, we still have to care about the pixel grid.
# Confusing metaphors
Icons might serve another function: to help users understand the meaning of the command.
For example, once you know the context (move window), these icons explain whatβs going on faster than words:
But for this to work, the user must understand whatβs drawn on the icon. It must be a familiar object with a clear translation to computer action (like Trash can β Delete), a widely used symbol, or an easy-to-understand diagram. HIG:
A rookie mistake would be to misrepresent the object. For example, this is how selection looks like:
But its icon looks like this:
Honestly, Iβve been writing this essay for a week, and I still have zero ideas why it looks like that. Thereβs an object that looks like this, but itβs a text block in Freeform/Preview:
Itβs called `character.textbox` in SF Symbols:
Why did it become a metaphor for βSelect allβ? My best guess is itβs a mistake.
Another place uses text selection from iOS as a metaphor. On a Mac!
Some concepts have obvious or well-established metaphors. In that case, itβs a mistake not to use them. For example, bookmarks: . Apple, for some reason, went with a book:
Sometimes you already have an interface element and can use it for an icon. However, try not to confuse your users. Dots in a rectangle look like password input, not permissions:
Icon here says βCheckβ but the action is βUncheckβ.
Terrible mistake: icon doesnβt help, it actively confuses the user.
Itβs also tempting to construct a two-level icon: an object and some sort of indicator. Like, a checkbox and a cross, meaning βDelete checkboxβ:
Or a user and a checkmark, like βCheck the userβ:
Unfortunately, constructs like this rarely work. Users donβt build sentences from building blocks you provide; they have no desire to solve these puzzles.
Finding metaphors is hard. Nouns are easier than verbs, and menu items are mostly verbs. How does open look? Like an arrow pointing to the top right? Why?
Iβm not saying thereβs an obvious metaphor for βOpenβ Apple missed. There isnβt. But thatβs the point: if you canβt find a good metaphor, using no icon is better than using a bad, confusing, or nonsensical icon.
Thereβs a game I like to play to test the quality of the metaphor. Remove the labels and try to guess the meaning. Give it a try:
Itβs delusional to think that thereβs a good icon for every action if you think hard enough. There isnβt. Itβs a lost battle from the start. No amount of money or βmanagement decisionsβ is going to change that. The problems are 100% self-inflicted.
All this being said, I gotta give Apple credit where credit is due. When they are good at choosing metaphors, they are good:
# Symmetrical actions
A special case of a confusing metaphor is using different metaphors for actions that are direct opposites of one another. Like Undo/Redo, Open/Close, Left/Right.
Itβs good when their icons use the same metaphor:
Because it saves you time and cognitive resources. Learn one, get another one for free.
Because of that, itβs a mistake not to use common metaphors for related actions:
Or here:
Another mistake is to create symmetry where there is none. βBackβ and βSee allβ?
Some menus in Tahoe make both mistakes. E.g. lack of symmetry between Show/Hide and false symmetry between completed/subtasks:
Import not mirrored by Export but by Share:
# Text in icons
HIG again:
Authors of HIG are arguing against including text as a part of an icon. So something like this:
or this:
would not fly in 1992.
I agree, but Tahoe has more serious problems: icons consisting _only_ of text. Like this:
Itβs unclear where βmetaphorical, abstract icon text that is not supposed to be read literallyβ ends and actual text starts. They use the same font, the same color, so how am I supposed to differentiate? Icons just get in a way: A...Complete? AaFont? What does it mean?
I can maybe understand and . Dots are supposed to represent something. I can imagine thinking that led to . But ? No decorations. No effects. Just plain Abc. Really?
# Text transformations
One might think that using icons to illustrate text transformations is a better idea.
Like, you look at this:
or this:
or this:
and just from the icon alone understand what will happen with the text. Icon _illustrates_ the action.
Also, BIU are well-established in word processing, so all upside?
Not exactly. The problem is the sameβtext icon looks like text, not icon. Plus, these icons are _excessive_. Whatβs the point of taking the first letter and repeating it? The word βBoldβ already starts with a letter βBβ, it reads just as easily, so why double it? Look at it again:
Itβs also repeated once more as a shortcut...
There is a better way to design this menu:
And it was known to Apple for at least 33 years.
# System elements in icons
Operating system, of course, uses some visual elements for its own purposes. Like window controls, resize handles, cursors, shortcuts, etc. It would be a mistake to use those in icons.
Unfortunately, Apple fell into this trap, too. They reused arrows.
Key shortcuts:
HIG has an entire section on ellipsis specifically and how dangerous it is to use it anywhere else in the menu.
And this exact problem is in Tahoe, too.
# Icons break scanning
Without icons, you can just scan the menu from top to bottom, reading only the first letters. Because they all align:
macOS Sequoia
In Tahoe, though, some menu items have icons, some donβt, and they are aligned differently:
Some items can have both checkmarks _and_ icons, or have only one of them, or have neither, so we get situations like this:
Ugh.
# Special mention
This menu deserves its own category:
Same icon for different actions. Missing the obvious metaphor. Somehow making the first one slightly smaller than the second and third. Congratulations! It got it all.
# Is HIG still relevant?
Iβve been mentioning HIG a lot, and you might be wondering: is an interface manual from 1992 still relevant today? Havenβt computers changed so much that entirely new principles, designs, and idioms apply?
Yes and no. Of course, advice on how to adapt your icons to black-and-white displays is obsolete. But the principlesβas long as they are good principlesβstill apply, because they are based on how humans work, not how computers work.
Humans donβt get a new release every year. Our memory doesnβt double. Our eyesight doesnβt become sharper. Attention works the same way it always has. Visual recognition, motor skillsβall of this is exactly as it was in 1992.
So yeah, until we get a direct chip-to-brain interface, HIG will stay relevant.
# Conclusion
In my opinion, Apple took on an impossible task: to add an icon to every menu item. There are just not enough good metaphors to do something like that.
But even if there were, the premise itself is questionable: if everything has an icon, it doesnβt mean users will find what they are looking for faster.
And even if the premise was solid, I still wish I could say: they did the best they could, given the goal. But thatβs not true either: they did a poor job consistently applying the metaphors and designing the icons themselves.
I hope this article would be helpful in avoiding common mistakes in icon design, which Apple managed to collect all in one OS release. I love computers, I love interfaces, I love visual communication. It makes me sad seeing perfectly good knowledge already accessible 30 years ago being completely ignored or thrown away today.
On the upside: itβs not that hard anymore to design better than Apple! Letβs drink to that. Happy New year!
From SF Symbols: a smiley face calling somebody on the phone
# Notes
During review of this post I was made familiar with Jim Nielsenβs article, which hits a lot of the same points as I do. I take that as a sign thereβs some common truth behind our reasoning.
Also note: Safari β File menu got worse since 26.0. Used to have only 4 icons, now itβs 18!
Thanks Kevin, Ryan, and Nicki for reading drafts of this post. https://tonsky.me/blog/tahoe-icons/
