Is Wish List One Word Or Two

If you have ever wondered whether to write “wish list” as one word or two, you are not alone—this spelling question trips up writers, shoppers, and digital marketers alike. And the debate over wish list one word or two comes down to how English handles compound nouns, and the answer often depends on which dictionary or style guide you follow. Still, in most formal writing, “wish list” remains two separate words, but you will frequently see “wishlist” written as a single word in app interfaces, e-commerce websites, and casual branding. Understanding the difference helps you choose the right form for your audience and context.

Is It “Wish List” or “Wishlist”? The Short Answer

The short answer is that “wish list” is traditionally two words, while “wishlist” is a newer, closed compound form that has gained popularity in digital and commercial spaces. Neither spelling is inherently “wrong,” but they serve different purposes.

• Wish list (two words): The standard form in most dictionaries, academic writing, journalism, and formal communication.
• Wishlist (one word): Common in tech, retail, software as a service (SaaS), and branding, where shorter compound words are often preferred for logos, buttons, and domain names.

If you are writing an essay, a news article, or a business report, stick with wish list as two words. If you are naming a mobile app feature, designing a website button, or creating a brand identity, wishlist as one word is widely accepted and often more visually compact.

Understanding Compound Words in English

English forms compound words in three main ways: open compounds, hyphenated compounds, and closed compounds. Knowing where “wish list” fits requires looking at these categories The details matter here..

Open Compounds

Open compounds are written as two separate words with a space between them. Examples include ice cream, post office, and wish list. These phrases function as a single unit of meaning even though they are not physically joined That alone is useful..

Hyphenated Compounds

Hyphenated compounds use a hyphen to link the words, such as mother-in-law, check-in, or long-term. Hyphenation often occurs when the compound acts as an adjective before a noun Not complicated — just consistent. Still holds up..

Closed Compounds

Closed compounds are written as one word with no space or hyphen. Examples include notebook, keyboard, and wishlist. Over time, many open compounds evolve into closed compounds as they become more familiar to speakers Not complicated — just consistent..

“Wish list” is currently in transition. It began as an open compound, but frequent use in digital environments has encouraged some writers and companies to treat it as a closed compound It's one of those things that adds up..

Dictionary Definitions and Usage Guides

Major reference sources offer useful guidance on the wish list one word or two question.

Merriam-Webster

Merriam-Webster lists “wish list” as an open compound (two words). It does not currently recognize “wishlist” as a standard entry in its collegiate dictionary, which means formal writing should default to the two-word version Easy to understand, harder to ignore..

Oxford English Dictionary

The Oxford English Dictionary also treats “wish list” as two words. It notes the phrase as a noun meaning a list of desired items, especially gifts or products.

Associated Press (AP) Stylebook

AP style generally prefers open compounds unless a word has been permanently closed in common usage. For “wish list,” AP would recommend two words in news and media copy Easy to understand, harder to ignore..

Chicago Manual of Style

Chicago follows a similar approach, favoring two words for open compounds that have not yet solidified into single words in general prose.

Because authoritative dictionaries and style guides still list “wish list” as two words, it remains the safer choice for academic, professional, and published writing.

When to Use “Wish List” (Two Words)

Use wish list as two words in the following situations:

• Academic essays and research papers: Formal writing benefits from the conservative, dictionary-backed spelling.
• Journalism and news articles: AP style and most editorial standards prefer two words.
• Business correspondence: Emails, reports, and proposals read more professionally with the standard spelling.
• Print books and magazines: Unless the publisher uses a house style that closes compounds, two words is the norm.

Example sentences:

• She added a new coffee maker to her wish list.
• The charity published a wish list of supplies needed for the shelter.
• Before the birthday party, the children made a long wish list of toys.

When “Wishlist” (One Word) Appears

You will encounter wishlist as one word primarily in digital and commercial contexts. This does not make it incorrect, but it does mark it as informal or industry-specific.

Common uses include:

• E-commerce websites: Online stores often label a feature “Add to Wishlist” to save space on buttons.
• Mobile applications: App developers prefer single-word labels for cleaner user interfaces.
• Brand names and logos: A company might call itself “Wishlist” or use the term in a domain name like wishlist.com.
• Social media and casual blogging: Informal writing often drops the space for speed and style.

Example sentences:

• Click the heart icon to save the item to your wishlist.
• Our new app lets you share your wishlist with friends.
• The startup rebranded as Wishlist to stress personal curation.

Digital Contexts and Branding

In user experience (UX) design, every pixel matters. A button that says “Add to Wishlist” fits more easily on a mobile screen than “Add to Wish List.” Because of this, many tech companies have adopted the one-word spelling as a convention, even if their formal press releases still use two words.

Branding also plays a role. A single word can be trademarked more easily than a two-word phrase, and it looks more distinctive in a logo. If

you are creating content for a general audience, the safest approach is to follow the standard. That said, reserve wishlist for your digital products, app interfaces, and casual social media posts. For everything else—from client emails to marketing copy for a physical product—stick with wish list And that's really what it comes down to..

In the long run, language evolves, and the one-word form may one day become the accepted standard. Plus, for now, the distinction remains a useful tool for writers and editors to signal tone and context. The choice is less about being right or wrong and more about being appropriate for your audience and medium.

In summary:

• Choose wish list for formal, professional, and published writing.
• Use wishlist for digital interfaces, brands, and informal online communication.

When in doubt, choose two words. It is the more conservative and widely accepted option, ensuring your writing remains clear and professional across all platforms.

Related Forms: When the Term Modifies a Noun

A separate question arises once the word starts working as an adjective. Standard editorial practice hyphenates a compound modifier that precedes a noun, so you might write:

• She sorted her wish-list items by priority.
• The campaign targeted wish-list shoppers in November.

If, however, you have already committed to the closed form for a product context, stay with it throughout: wishlist button, wishlist feature, wishlist data. Mixing wish-list and wishlist as modifiers within the same document is the most common inconsistency editors catch The details matter here..

Regional and Editorial Variation

Major American dictionaries continue to list wish list as the primary spelling, with the closed form noted as a variant. British usage guides take a similar position, though they tend to be slightly more tolerant of single-word forms in computing. Corpus data tells the real story: the closed spelling has climbed steeply since roughly 2010, driven almost entirely by retail sites, gaming platforms, and app copy. Dictionaries generally lag behind shifts like this by several years, so a spelling that looks "wrong" today may look unremarkable a decade from now.

Parallel Compounds Worth Watching

English has a whole family of open compounds with list: gift list, shopping list, bucket list, *

Parallel Compounds Worth Watching

English is rich with open compounds that pair a noun with list. The pattern is intuitive—something you compile or review is naturally expressed as a “list of X.” While many of these stay open, a few have drifted toward closed or hyphenated forms, offering a useful mirror for the wish‑list debate:

This is the bit that actually matters in practice.

These examples illustrate two broader trends:

1. Digital UI conventions often favor closed forms for brevity and to fit tight interface real‑estate. A “wishlist button” looks cleaner than “wish‑list button” on a mobile screen, and developers naturally adopt the closed spelling for class names, database fields, and API endpoints Nothing fancy..

2. Print and formal prose retain the open spelling to preserve readability and to avoid unintentionally creating a trademarked single word. Editors therefore default to “wish list” in books, articles, and official documents.

The wish‑list split mirrors these patterns. When the term functions as a noun describing a collection (e.Consider this: g. , “She added the novel to her wish list”), the open spelling is the safest choice. Day to day, when it serves as a modifier preceding a noun (e. g., “wish‑list items”), standard style guides prescribe a hyphen.

When developers translate the linguistic nuance of “wish‑list” into code, they usually encounter three distinct situations. Second, when it modifies a noun, such as “the wish‑list entries you can edit,” the hyphenated form signals that the term acts as an adjective or qualifier, echoing the typographic habit found in print and formal writing. Worth adding: first, if the word appears as a standalone noun—say, “She placed the novel on her wish list*”—the expanded spelling preserves the visual separation between multiple items and aligns with style guides that prefer spaces for enumerations. Third, inside a product’s own terminology—where designers have already chosen the compact spelling for menus, checkboxes, or backend routes—the closed form becomes entrenched and simplifies navigation for power users Practical, not theoretical..

These practical choices ripple through several layers of development. On the flip side, function signatures and event handlers often follow the modifier rule: submitItem(wishlist, item) reads naturally because “wishlist” describes what will be submitted, whereas submitToWishlist(item) feels mechanical. Database columns that store collections benefit from clear naming: user_wish_list_items conveys a plural set without ambiguity, while wishlists could imply multiple rows Most people skip this — try not to..

And yeah — that's actually more nuanced than it sounds It's one of those things that adds up..

API endpoints typically mirror resource orientation; a GET request to /wishlist/123 treats the entity as singular, whereas /wish-lists/123 suggests a collection of items—a pattern reinforced by RESTful conventions that employ plural nouns for collections and singular nouns for individual resources. Day to day, when the closed form dominates a product’s internal vocabulary, developers often align endpoint URLs with that convention, using /wishlist for a single user’s list and /wishlists for the aggregate view that aggregates multiple users’ lists or provides bulk operations. This alignment reduces cognitive friction: a power user who sees “wishlist” in the navigation menu can immediately map the same token to the API path, simplifying both discovery and debugging Not complicated — just consistent..

Beyond URL design, the spelling choice influences data modeling and serialization. In JSON payloads, a field named wishlist naturally conveys a single list object, while wishlists signals an array. On top of that, consistency between the naming in the contract and the terminology presented to end‑users helps prevent mismatches that can cause subtle bugs in client‑side state management. Here's the thing — for example, a front‑end component that renders “Your wishlist” may bind to a prop called wishlistItems; if the back‑end endpoint returns wishlist, the developer must remember to pluralize the data shape, which can introduce off‑by‑one errors in loops or conditional checks. By deliberately choosing the same morphological form across the stack—whether open, hyphenated, or closed—teams create a mental model that is easier to reason about and less prone to misinterpretation That's the part that actually makes a difference..

Testing strategies also adapt to the chosen spelling. But unit tests that assert the correct request URL often include the exact path string, so a shift from /wishlist to /wish-lists requires updating a suite of expectations. Here's the thing — automated documentation generators, which parse route definitions to produce developer portals, will render the hyphenated version as two separate segments, potentially breaking the perceived hierarchy. So naturally, teams that adopt the closed form must check that their documentation pipelines treat the hyphen as a word separator rather than a literal delimiter, otherwise the generated spec may mislead consumers.

From a broader product perspective, the decision between open, hyphenated, and closed spellings can affect branding and searchability. Conversely, a brand that embraces the open form might rank higher for queries containing a space, such as “wish list ideas,” because search engines treat the space as a natural delimiter. Still, a trademarked “WishList” logo that uses the closed form may dominate search engine results, pushing organic queries toward the same spelling. Marketing teams therefore often conduct A/B tests on landing‑page copy that feature either spelling, measuring click‑through rates and conversion metrics to determine which variant resonates more with the target audience.

Boiling it down, the linguistic nuances of “wish‑list” extend far beyond stylistic preference; they shape how developers name functions, structure databases, design APIs, write tests, and even market the product. By consciously selecting the form that best matches the term’s role—noun versus modifier—and by maintaining consistency across the entire technology stack, teams achieve clearer communication, fewer integration headaches, and a more cohesive user experience. The careful balance between brevity in code and readability in documentation ensures that the term serves its purpose efficiently, whether it appears as a single word in a mobile UI, a hyphenated qualifier in a style guide, or an open phrase in a printed manual.