Have you ever stared at a checkbox, a dropdown menu, or a UI button and wondered should this say unselect or deselect? You’re not alone. Thousands of technical writers, UX designers, developers, and everyday users face this exact question.
While both words appear to describe the same action removing a previously made selection they are not interchangeable in professional and technical contexts.
This comprehensive guide breaks down the difference between unselect vs deselect, explains the grammar behind each term, reviews how major tech companies like Microsoft, Apple, and Google handle this distinction, and gives you clear, practical guidance for every situation.
Whether you’re writing software documentation, designing a user interface, or simply trying to get your English right, this article has you covered.
What Does “Deselect” Mean?
Deselect is a verb that means to remove or reverse a previously made selection in a digital interface, form, or application. If you click a checkbox to check it and then click it again to uncheck it, you have deselected it.
The word is formed from the Latin-based prefix de-, which signals a deliberate reversal or removal of a prior action. Think of similar technical terms: deactivate, detach, decompress, deregister. All of them follow the same pattern: the de- prefix clearly communicates that something is being undone in a formal, precise way.
Example Sentences Using “Deselect”
- “Deselect all checkboxes before submitting the form.”
- “To remove a filter in Google Sheets, deselect the rows you no longer need.”
- “Press Ctrl+D in Adobe Photoshop to deselect an active selection.”
- “In Microsoft Word, deselect highlighted text by clicking anywhere else in the document.”
- “The user deselected three options before proceeding to checkout.”
Deselect has been documented in major dictionaries and has been the standard term in software interfaces since graphical user interfaces became mainstream in the 1990s. It is used consistently in official documentation from Microsoft, Apple, Google, and Adobe and appears in authoritative style guides including the Microsoft Manual of Style and Apple Human Interface Guidelines.
Click Here To Read Invision vs Envision
What Does “Unselect” Mean?
Unselect is an informal verb that also describes the action of removing a previously made selection. It is built from the prefix un-, which in English typically signals the reversal of a state: think undo, unmute, unfriend, uncheck.
The logic seems perfectly intuitive: if select means to choose something, then unselect must mean to unchoose it. And in everyday conversation or casual writing, most people understand exactly what you mean.
However, there’s a linguistic catch. The un- prefix in English is most correctly applied to reverse states rather than deliberate actions. When you select something, you perform an action; you don’t just enter a state. This is why formal English grammar and technical style guides favor de- for intentional reversals of actions over un-, which is more suited to reversing conditions or states.
Example Sentences Using “Unselect”
- “Tap the box again to unselect it.” (informal mobile UI instruction)
- “I accidentally unselected the file and had to start over.” (casual speech)
- “Users can unselect the checkbox to disable notifications.” (informal tutorial)
These sentences are perfectly understandable, but they would typically be revised to use deselect in any professional or formal documentation context.
Unselect vs Deselect: Side-by-Side Comparison
The table below summarizes the key differences between these two terms across the dimensions that matter most to writers, designers, and developers.
| Feature | Deselect | Unselect |
| Formality | Formal, professional | Informal, casual |
| Dictionary Recognition | Yes Merriam-Webster, Oxford, Cambridge | No absent from major dictionaries |
| Prefix Origin | Latin de- (deliberate reversal of action) | Old English un- (reversal of state) |
| Used in Style Guides | Yes Microsoft, Apple, Google | No |
| Industry Standard | Yes dominant in technical writing | No considered nonstandard |
| UX Writing Recommendation | Strongly preferred | Discouraged in professional contexts |
| Developer Usage | Dominant in APIs, frameworks, naming | Occasionally found in legacy codebases |
| Screen Reader Compatibility | Consistent and accessible | May cause inconsistencies |
| Search Volume | ~10x more than “unselect” | Significantly lower |
| Localization | Maps cleanly to other languages | Can create translation inconsistencies |
The Grammar Argument: Why “Deselect” Wins
Understanding why deselect is the grammatically preferred choice requires a quick look at how English prefixes work.
The Role of “De-” vs “Un-“
In standard English:
- De- is used to reverse deliberate, action-based processes: decode, deactivate, detach, deregister, decompress
- Un- is typically used to reverse states or conditions: unhappy, unknown, unsafe, uncheck (unchecking refers to a visual state, not a process)
Because selecting is a deliberate action performed by a user not simply a state that something passively enters the prefix de- is the grammatically correct choice for its reversal. This is the same reason we say deactivate (not unactivate) and detach (not unattach).
Interestingly, uncheck is widely accepted because “checking” a box is often understood as a visual state (the checkmark is either there or it isn’t), making the un- prefix slightly more defensible there. But selection in computing is consistently treated as an intentional act, which is why deselect holds up under grammatical scrutiny.
What Do Major Tech Companies Say?
When in doubt, it helps to look at how the world’s largest technology companies handle the question. Their style teams spend years researching language clarity, user behavior, and terminology consistency so their choices carry significant weight.
Microsoft
The Microsoft Style Guide is explicit: use deselect when referring to clearing a checkbox or reversing a selected state. Microsoft avoids unselect entirely across their documentation, UI text standards, and product interfaces. Their reasoning is simple: unselecting introduces ambiguity, especially for non-technical users.
Apple
The Apple Human Interface Guidelines maintain consistent use of deselect across macOS, iOS, and iPadOS. Whether it’s clearing selected objects in a list, reversing a toggled checkbox, or removing highlighted text, Apple’s documentation uses deselect as the standard term.
Google’s developer documentation and Material Design guidelines favor deselecting for all multi-select UI components, toggles, and list interactions. From Google Sheets help documentation to Android design specs, the term of choice is consistently deselected. Google Docs help text reads: “To deselect a cell, hold down Ctrl and click it” not unselect.
Adobe
Adobe’s Photoshop documentation uses deselect universally. The standard keyboard shortcut to remove an active selection Ctrl+D on Windows or Cmd+D on Mac is described as the Deselect command in every version of the product.
Unselect vs Deselect in UX Writing
For UX writers, the choice between these two words is not just about grammar it directly affects how users interact with products. Clarity is the foundation of good UX microcopy, and even a single word can influence whether a user completes a task successfully.
Why “Deselect” Performs Better in User Interfaces
Research in UX writing supports a clear preference for deselect over unselect:
- Users recognize deselect faster, with fewer moments of hesitation
- Survey data from UX usability testing shows “Deselect All” outperforms “Unselect All” by approximately 23% in task completion accuracy
- Screen readers handle deselect more consistently, which matters for accessibility compliance
- International users find deselect easier to process because it follows predictable technical vocabulary patterns
- Localization teams can map deselect more cleanly to equivalents in Spanish (deseleccionar), French (désélectionner), and German (Auswahl aufheben)
The Dropbox Case Study
One practical example comes from Dropbox’s early onboarding flow, which used uncheck in tutorial instructions. After usability testing, the UX team switched to deselect after finding users associated “check” with verification rather than selection. The result: users clicked the correct checkbox 22% more often. This illustrates how word precision directly translates into measurable product improvements.
Guidance from Industry Experts
Torrey Podmajersky, author of Strategic Writing for UX, emphasizes that clarity is the most important quality in UI text writers should use words that already exist in the user’s mental vocabulary. In technical interfaces, deselect is that word.
When Is “Unselect” Acceptable?
Despite its informal status, there are a handful of situations where unselect appears without causing meaningful harm and in some cases, where changing it would actually create more friction than it resolves.
Acceptable Uses of “Unselect”
- Internal codebase or legacy APIs Some older frameworks, libraries, and Java Swing implementations used .unselect() methods. If you’re maintaining existing code with that convention, consistency matters more than terminology preference. Changing all instances could break things.
- Casual tutorials and forum posts When writing for informal audiences in personal blogs, community forums, or quick how-to notes, either term is understood. Nobody will misinterpret your meaning if you say unselect in a Reddit thread.
- Space-constrained UI labels In rare cases where character limits in button labels are extreme and every character counts, either term works practically. However, deselect contains only one additional character, so this justification is rarely strong.
- Matching existing product language If you’re writing documentation for a product that already uses unselect throughout its interface and codebase, adopt the existing convention to avoid confusing your audience with inconsistent terminology.
Practical Usage Guide: When to Use Which Term
Use the following decision framework when you encounter this choice in your work:
Use “Deselect” When:
- Writing technical documentation or software manuals
- Designing UI microcopy, button labels, or tooltip text
- Creating onboarding flows or help center articles
- Writing for a multilingual or international audience
- Building accessible interfaces (screen reader compatibility)
- Working within a formal style guide or brand voice guidelines
- Writing API documentation or developer guides
- Creating educational content about software tools
Use “Unselect” (or Consider It) When:
- The existing codebase or product already uses it consistently
- Writing in an informal, conversational context (chat, personal blog, forums)
- Maintaining legacy documentation where changing the term would create confusion
- Internal team notes or communications where precision is secondary to speed
Alternative Plain-Language Options
In some contexts, especially consumer-facing products, educational software, or apps designed for non-technical users neither deselect nor unselect may be the clearest choice. Consider these plain-language alternatives:
- Uncheck Specifically for removing a checkmark from a checkbox
- Clear For removing input or selections from form fields (e.g., “Clear all filters”)
- Remove When an item is being taken out of a selection group
- Toggle off For switching a feature or setting from active to inactive
- Click to deselect When additional context helps the action feel intuitive
Real-World Examples From Major Software Platforms
Seeing how leading software products actually apply this terminology removes any remaining ambiguity.
| Platform | Example Documentation Text |
| Microsoft Word | “Deselect highlighted text by clicking anywhere else in the document.” |
| Adobe Photoshop | “Press Ctrl+D to deselect the active selection.” |
| Google Sheets | “To deselect a cell, hold down Ctrl and click it.” |
| Google Docs | “Click ‘Select All’ again to deselect all text.” |
| Microsoft Excel | “To deselect multiple cells, hold Ctrl and click the selected cells.” |
| Fortnite (Gaming UI) | “Deselect Item” used in inventory and loadout menus |
| Apple macOS | “Deselect when clearing selected objects.” (Apple HIG) |
In every single case above, the term is deselect not unselect.
The Historical Context: How “Deselect” Became Standard
Understanding where these terms come from helps explain why one won out over the other.
Early computing software, including Lotus 1-2-3 and early versions of Microsoft Excel, introduced the phrase “Deselect All” as a standard UI control for clearing selections. As graphical user interfaces spread throughout the 1990s, software needed clear, consistent language for describing user actions and deselect became the dominant choice precisely because the de- prefix aligned with existing technical vocabulary patterns.
Some early Java Swing APIs used .unselect() method names internally, which is why some developers picked it up as shorthand. But as software documentation matured, industry-wide standardization on deselect took hold reinforced by major platform style guides, cross-platform UI consistency requirements, and the needs of localization teams.
By the 2000s and 2010s, deselect had become entrenched as the documentation default, particularly in multilingual software environments where clarity and standardization were critical. Google Ngram data shows deselect rising sharply in published usage during the 1990s, while unselect remained essentially flat throughout the same period.
Common Mistakes to Avoid
Even careful writers occasionally trip up on this distinction. Here are the most frequent errors and how to fix them.
Mistake 1: Using “unselect” in formal documentation
- ❌ “Users can unselect the items they don’t want.”
- ✅ “Users can deselect the items they don’t want.”
Mistake 2: Confusing “deselect” with “delete” or “remove”
- ❌ “Deselect the file from your hard drive.” (this implies deletion)
- ✅ “Deselect the file to remove it from the active selection.” (clarifies no deletion occurs)
Mistake 3: Inconsistency within one document or interface
- ❌ Using deselect in one paragraph and unselect two paragraphs later
- ✅ Pick one term and use it consistently throughout
Mistake 4: Applying “deselect” to non-selection contexts
- ❌ “Deselect the settings you want to keep.” (confusing should be “update” or “configure”)
- ✅ “Deselect the options you no longer want enabled.”
Frequently Asked Questions
Is “unselect” a real word?
Unselect is technically a formed word, but it is not recognized in major dictionaries like Merriam-Webster, Oxford, or Cambridge. It exists in casual usage and informal contexts but lacks formal linguistic standing.
Which term is correct: unselect or deselect?
Deselect is the correct, standard term for professional and technical writing. It is dictionary-recognized, style-guide approved, and used consistently by Microsoft, Apple, Google, and Adobe.
Can I use “unselect” in my code?
Yes, if your existing codebase already uses it. However, for new APIs, public-facing documentation, or naming conventions in shared codebases, deselect is the recommended choice for clarity.
Do Microsoft and Google officially use “deselect”?
Yes. Both Microsoft and Google use deselect consistently across their official documentation, style guides, and product interfaces. Neither company uses unselect in formal materials.
Is “deselect” the same as “uncheck”?
Not exactly. Deselect is a broader term for removing any kind of selection, while uncheck specifically refers to removing a checkmark from a checkbox. Use uncheck when referring specifically to checkboxes; use deselect for other types of selections.
Which term is better for accessibility?
Deselect is the better choice for accessibility. It is consistent, dictionary-backed, and processed more reliably by screen readers and assistive technologies.
What are plain-language alternatives to deselect?
Good alternatives include uncheck (for checkboxes), clear (for form fields), remove (for selection groups), and toggle off (for settings or features).
Is “Deselect All” the correct phrasing?
Yes. “Deselect All” is the universally accepted phrase for removing all active selections. “Unselect All” is rarely seen in professional software and is considered nonstandard.
Conclusion
The debate between unselect vs deselect has a clear answer for anyone writing professionally: deselect is the correct, standard, and universally accepted term.
It is backed by dictionary recognition, validated by the style guides of the world’s leading technology companies, preferred in UX research, and consistent with the grammatical logic of the English prefix system. When you use deselect in your documentation, interfaces, or instructions, you signal precision, professionalism, and alignment with industry standards.
Unselect is not a cardinal error; it won’t cause misunderstanding in casual conversation or informal tutorials. But in any formal technical documentation, UI microcopy, API references, onboarding flows, or user guides unselect introduces unnecessary ambiguity and breaks the consistency your audience expects.
The rule is straightforward: default to deselect in all professional contexts, reserve unselect only for existing informal conventions where changing the term would create more confusion than it resolves, and consider plain-language alternatives like uncheck or clear when your audience needs maximum accessibility.
Get this one word right, and your documentation instantly looks more polished, credible, and user-friendly.
