Unselect vs. Deselect: Which Word Should You Actually Use?
If you’ve ever written UI copy, help docs, or a checkbox instruction, you’ve probably paused on this one: do you tell users to “deselect” an item, or “Unselect vs. Deselect” it? They sound like twins, but only one of them is standard English and picking the wrong one, even by accident, can chip away at how polished your product feels.
Here’s the clear breakdown.
The Short Answer
Deselect is the correct, dictionary-recognized term. Unselect is a word people understand, but it’s informal and hasn’t earned a spot in most style guides or major dictionaries. When you’re writing anything user-facing buttons, tooltips, documentation deselect is the safer, more professional choice.
Where the Confusion Comes From
Once “select” became a common action in software, someone needed a word for its opposite. Two candidates showed up naturally:
- de- as a prefix, meaning “reverse” or “undo” (as in decode, defrost, deactivate)
- un- as a prefix, also meaning “reverse” (as in undo, unlock, unpack)
Both prefixes are legitimate in English, which is exactly why both words feel right. But usage over time settled on “deselect” as the one that stuck in formal and technical writing, while “unselect” lingered mostly in casual developer speak and older software.
Why “Deselect” Won Out
Words earn a permanent place in the dictionary through consistent, widespread use across time not just because they’re grammatically possible. “Deselect” checks those boxes:
- It shows up consistently in major software from Microsoft, Google, Apple, and Adobe.
- It’s the term UX writing guidelines typically recommend.
- It reads clearly to both native and non-native English speakers, which matters a lot for localization.
“Unselect” isn’t incorrect in the sense of breaking grammar rules English forms new words with “un-” all the time. It just never reached the same level of formal recognition. Think of it like “irregardless”: people use it, people understand it, but it’s still considered nonstandard next to “regardless.”
Side-by-Side Comparison
| Deselect | Unselect | |
|---|---|---|
| Recognized in major dictionaries | Yes | Largely no |
| Used by major tech platforms | Yes, consistently | Occasionally, mostly legacy tools |
| Recommended for UI/documentation | Yes | No |
| Grammatically valid | Yes | Yes, but nonstandard |
Seeing Both in Action
With “deselect” (recommended):
- “Click the checkbox again to deselect it.”
- “Use Ctrl+Click to deselect individual rows.”
- “Deselect all filters to reset your search.”
See More https://reuterings.co.uk/how-to-vs-how-tos/
With “unselect” (common but not ideal):
- “Press Esc to unselect everything.”
- “Tap the item again to unselect it.”
Both versions communicate the same idea. The difference is polish “deselect” reads like it belongs in a finished product; “unselect” reads like a placeholder that never got updated.
When You Might Still See “Unselect”
It’s not that “unselect” is banned it just tends to survive in specific pockets:
- Legacy codebases where the term was baked in early and never revisited
- Developer comments and internal tooling, where precision matters less than speed
- Products without an established style guide, where whoever wrote the button text just went with instinct
None of these are reasons to keep it in new, user-facing writing.
Sometimes, Skip Both
Not every situation needs “deselect” or “unselect” at all. Depending on context, a different verb might communicate the action more naturally:
| Alternative | Works well for |
|---|---|
| Clear | Filters, form fields |
| Untick | Checkboxes (especially in UK English) |
| Turn off | Toggles, switches |
| Cancel | File pickers, photo tools |
| Remove selection | Longer, instructional sentences |
For example, “Clear all filters” often reads more naturally in a UI than “Deselect all filters” shorter, punchier, and just as clear.
Why This Actually Matters
This might feel like a minor wording choice, but inconsistency adds up. If one screen in your product says “deselect” and another says “unselect,” users may wonder even subconsciously whether the two actions behave differently. Translators hit the same snag, since inconsistent terms in the source text often get translated inconsistently too. Small wording gaps like this quietly increase the mental effort it takes to use a product.
Quick FAQ
Is “unselect” a real word? It’s understood and used informally, but it isn’t standard English the way “deselect” is.
Which one should I use in professional or technical writing? Deselect it’s the recognized, consistent choice across major software and style guides.
Why do some apps still use “unselect”? Usually because the term was written early on and never revisited, or the product never adopted a formal style guide.
Are there better alternatives to both? Yes depending on context, “clear,” “untick,” “turn off,” or “cancel” can be more natural and concise.
Bottom Line
Both words are understandable, but only “deselect” carries dictionary backing and professional consistency. When precision and polish matter and in UI writing, they always do deselect is the term to standardize on.
