--- title: "British Spelling of Color: 'Colour' vs. 'Color' Explained" description: "Master the British spelling of color ('colour') & its difference from US 'color'. Get usage rules for global writing, regional variants, and style guides." url: "https://rewritebar.com/articles/british-spelling-of-color" --- [Back to Articles](https://rewritebar.com/articles "Back to Articles") July 20, 2026[Auditorial](https://rewritebar.com/blog/category/auditorial "Posts in Auditorial") # British Spelling of Color: 'Colour' vs. 'Color' Explained Master the British spelling of color ('colour') & its difference from US 'color'. Get usage rules for global writing, regional variants, and style guides. Written by [![Avatar of Mathias Michel](https://rewritebar.com/_next/image?url=%2F_next%2Fstatic%2Fimmutable%2Fmedia%2Fmathias.35h56kwevcs7u.jpg&w=64&q=75)Mathias Michel](https://rewritebar.com/blog/author/mathias "Posts by Mathias Michel") More to read [Mastering Articles in Grammar for Better Writing](https://rewritebar.com/articles/articles-in-grammar "Mastering Articles in Grammar for Better Writing") Master articles in grammar with clear rules for definite, indefinite, and zero articles. Learn exceptions, avoid common errors, and practice with AI tools. [Commas in Compound Sentences: A Clear Guide for 2026](https://rewritebar.com/articles/commas-in-compound-sentences "Commas in Compound Sentences: A Clear Guide for 2026") Master commas in compound sentences with this clear guide. Learn the rules, avoid common mistakes, and improve your writing today. [Custom Keyboard Shortcuts Mac: A Practical Guide](https://rewritebar.com/articles/custom-keyboard-shortcuts-mac "Custom Keyboard Shortcuts Mac: A Practical Guide") Learn to set custom keyboard shortcuts Mac with our practical guide—covering system settings, Quick Actions, third-party tools, and conflict fixes. Published July 20, 2026 Tags [Grammar](https://rewritebar.com/articles/tags/grammar)[Writing Tips](https://rewritebar.com/articles/tags/writing-tips)[Common Mistakes](https://rewritebar.com/articles/tags/common-mistakes)[Workplace Writing](https://rewritebar.com/articles/tags/workplace-writing) ![British Spelling of Color: 'Colour' vs. 'Color' Explained](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/50e82519-fcdd-4708-9940-45732e0916cb/british-spelling-of-color-linguistics-comparison.jpg) **Colour** with a **u** is the standard British spelling, and **color** without a **u** is the American spelling. If you're writing for a UK audience, use **colour**. If you're writing for a US audience, use **color**. That's the simple rule. The harder part is what to do when your reader is in London, your client is in Toronto, your investor is in San Francisco, and your product docs are read everywhere. For a modern writer, the british spelling of color isn't just a schoolbook distinction anymore. It affects trust, consistency, localization, and, in technical contexts, even how teams structure documentation and UI copy. ## Color vs Colour The Fundamental Difference You type “color,” your editor throws up a red underline, and now you're second-guessing the whole sentence. That usually means your app, browser, or document is set to British English. The core distinction is straightforward: - **British English:** colour - **American English:** color That's the commonly sought answer. But in practice, the choice matters because readers notice these details fast, especially in product copy, landing pages, help docs, and client-facing writing. ![A person using a laptop to type the word color in a Microsoft Word document.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/78ba150d-d9ef-4e42-89ff-96cd5ce23bc8/british-spelling-of-color-word-processor.jpg) ### What the rule looks like in real writing If you're writing any of the following for a British audience, **colour** is the expected form: - **UI text:** “Choose a colour theme” - **Marketing copy:** “Add colour to your brand” - **Academic or formal writing:** “The use of colour in design” - **Support docs:** “Change the colour settings” For US readers, the equivalent spelling is **color** in each case. > **Practical rule:** Match the spelling to the reader, not to your personal habit. That matters more than many writers expect. A single word rarely breaks comprehension, but repeated dialect mismatch makes writing feel off. In consumer-facing work, “off” is enough to make a page feel imported, generic, or lightly unedited. ### Why this still trips people up The british spelling of color looks like a tiny variation, but it sits inside a larger spelling system. Once you choose one dialect, other words tend to follow it. If you write **colour**, you'll often also write **favour**, **honour**, and **labour**. If you write **color**, you'll usually write **favor**, **honor**, and **labor**. That's why this isn't just a one-word decision. It's a consistency decision. ## The Historical Divide Why Two Spellings Exist The split between **colour** and **color** didn't happen by accident. Two influential dictionaries pushed English in different directions. In Britain, Dr. Samuel Johnson's _Dictionary of the English Language_, published in **1755**, cemented **colour** as the standard British spelling, selecting the Anglo-Norman form _culur_ over the Latin _color_ as the standard orthography, as explained in this [history of color and colour spelling](https://grammarguide.blog/color-vs-colour-understanding-the-spelling-difference-with-clear-examples/). ![A timeline chart illustrating the historical development and divergence of British and American English spelling systems.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/82f1c14d-c72c-4cd3-a7e5-042df39d446f/british-spelling-of-color-language-history.jpg) ### Johnson fixed the British standard Johnson didn't invent the word. The **\-our** form had already been common in Britain since the **14th century**. What he did was give that spelling authority. Once a dictionary becomes the reference point for publishers, teachers, and government writers, its choices spread. That's what happened with **colour**, and the same pattern held for words like **favour**, **honour**, and **labour**. > British spelling often feels “traditional” because it was formalized through reference works that publishers treated as standard. ### Webster reshaped the American version Across the Atlantic, Noah Webster pushed a different idea of English. The American variant **color** was systematized through **19th-century** lexicographic reforms, and Webster explicitly targeted words like **honour** and **colour** for simplification, as described in this [account of Webster's spelling reforms](https://www.facebook.com/groups/tastecolorofbansko/posts/1454087746053931/). Webster's reforms weren't random. They reflected a preference for simpler forms and helped establish a separate American standard. By the time his dictionary took hold, **color** was no longer just an alternative spelling. It had become the expected one in US English. ### Why the history still matters This background explains something useful for modern writers. Neither spelling is “more correct” in absolute terms. Each belongs to a different standard. That's why arguments about whether **colour** is old-fashioned or **color** is wrong miss the point. These are stable regional conventions, created by deliberate editorial choices and preserved by schools, publishers, and style guides. ## Common -Our vs -Or Word Pairs and Exceptions Once you know **colour/color**, the broader pattern becomes easier to spot. Many British **\-our** words lose the **u** in American English. ### Common British and American pairs | British English (-our) | American English (-or) | | ---------------------- | ---------------------- | | colour | color | | favour | favor | | honour | honor | | labour | labor | | humour | humor | | neighbour | neighbor | This pattern lines up with the broader simplification associated with American spelling reform. Webster's system didn't just affect **colour**. It also shaped related words in the same family. ### The pattern helps, but don't overapply it Writers get into trouble when they assume every **\-or** word in British English should gain a **u**. That isn't how it works. Words such as **horror**, **tremor**, and **mirror** don't become _hourrour_, _tremour_, or anything similar in British English. The **\-our/-or** split applies to specific word histories, not to every word ending in those letters. A few practical points keep you out of trouble: - **Use families carefully:** If you've chosen **colour**, check related terms like **favour** and **honour** too. - **Watch adjacent spelling systems:** A page with **colour** often also prefers **centre** over **center**. This guide on [centre or center](https://rewritebar.com/articles/centre-or-center) is a useful companion. - **Trust dictionaries over instinct:** Some words don't follow the pattern cleanly, and habit is a poor editor. > A reliable style decision beats a half-remembered rule every time. ### What usually doesn't work What fails most often is mixing spellings in the same document. A sentence like “Choose your favourite color theme” looks careless because it blends two systems. Readers may not always be able to name the issue, but they notice the inconsistency. In branded writing, that's enough reason to fix it. ## How to Choose the Right Spelling for Your Audience The best spelling choice depends on **who's reading**, **where the text appears**, and **whether the document has to stay consistent across markets**. ![A businesswoman thoughtfully looking at a strategic marketing flowchart drawn on a whiteboard in an office.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/67eff7f1-e526-404e-8829-1d78a29e3122/british-spelling-of-colour-marketing-flowchart.jpg) For solo writers, the decision is usually easy. UK client, use **colour**. US client, use **color**. Global publishing makes it messier. A verified claim from Scribbr's cited angle is especially useful here. **Inconsistent spelling in global docs increases comprehension errors by 18% for non-native readers**, and no major grammar tool currently offers context-aware switching based on reader location rather than writer location, according to this [discussion of color or colour in global writing](https://www.scribbr.co.uk/uk-vs-us/color-or-colour/). ### Start with the reader, not the writer A Singapore-based founder writing a pitch for US investors may be better served by **color**. The same founder writing onboarding emails for UK customers may need **colour** instead. That's the core decision model: 1. **Primary market** If most readers are British or in Commonwealth contexts, use **colour**. 2. **House style** If your company already follows a style guide, follow it even if it isn't your native spelling. 3. **Platform context** Product copy, app strings, and documentation often need localization rules rather than one global default. For teams handling translated or regionalized content, these [localization best practices](https://rewritebar.com/articles/localization-best-practices) matter more than personal preference. ### Consistency beats cleverness Some writers try to split the difference. They'll use **color** in code comments and **colour** in marketing pages, or switch depending on the sentence. That usually creates more maintenance work, not less. Pick one standard per asset, then apply it everywhere in that asset. > If the page is for one audience, one spelling system is almost always the right call. This short explainer is useful if you want a quick reset on the broader distinction before setting editorial rules: ### A practical framework that holds up Use **colour** when: - **The audience is UK or Commonwealth-based** - **The publication follows British house style** - **The brand wants local familiarity** Use **color** when: - **The audience is primarily American** - **The content sits inside US-centric tech or startup ecosystems** - **You need consistency with existing American documentation** For mixed audiences, choose one standard at the publication level and stick to it. That's usually better than trying to personalize every page manually. ## Spelling Beyond the UK and US The british spelling of color doesn't stop at Britain. In many markets, **colour** is the expected form even when the audience isn't in the UK. Canada and Australia are the obvious examples. In broad terms, they sit closer to British spelling traditions than American ones, especially for words like **colour** and **favour**. But writers shouldn't assume these markets are identical to Britain in every spelling choice. ### Commonwealth spelling in product and UI work In technical writing and software localization, style guides matter more than national stereotypes. Style guides such as the Microsoft Manual of Style and Apple Human Interface Guidelines explicitly require **colour** for UK and Commonwealth locales and **color** for US locales in UI text, documentation, and error messages, as summarized in this [overview of color vs colour in major style guides](https://www.grammarly.com/blog/commonly-confused-words/color-colour/). That has a practical consequence for product teams. If your app supports locale-specific English, your strings should too. - **en-GB:** colour - **en-CA:** colour - **en-AU:** colour - **en-US:** color ### Canada is often the trickiest market Canada often blends British and American habits, which can mislead non-native writers. A page aimed at Canadian users may still prefer **colour**, even when other word choices on the same site feel closer to US English. If you're also dealing with related regional terms, this comparison of [cheque vs check](https://rewritebar.com/articles/cheque-vs-check) shows how quickly these choices branch beyond one word. > Regional English isn't binary. Canada and Australia often follow British spelling while absorbing American influence in other areas. The safe approach is simple. Don't guess from geography alone. Check the brand style, locale, or publication standard first. ## Modern Trends and Style Guide Recommendations Traditional style guidance is still clear. British references prefer **colour**. American style systems prefer **color**. In formal publishing, education, and region-specific marketing, that rule still works well. What's changing is the technical layer around writing. In developer docs, API descriptions, README files, and code-adjacent content, many teams now default to the shorter American form even outside the US. ### Why tech teams increasingly choose color A **2025** analysis of **10,000 GitHub READMEs** found that **“color” usage rose from 62% to 78% in non-US repos**, including repositories in Commonwealth countries like Canada and Australia, according to this [analysis of color and colour usage in technical contexts](https://grammarist.com/spelling/color-colour/). That doesn't mean **colour** has stopped being correct. It means some technical teams are optimizing for a different standard: shorter tokens, code consistency, and alignment with US-heavy developer ecosystems. ![An infographic comparing British English and American English style guides for professional writing and spelling preferences.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/e9a185c8-fddc-40d0-99ce-5cf16805b15c/british-spelling-of-color-language-comparison.jpg) ### What to do with that trend If you write essays, proposals, public-facing regional copy, or UK-targeted pages, **colour** remains the right British spelling. If you write code comments, developer docs, schema fields, or cross-border startup documentation, **color** may be the operational default even for globally distributed teams. The useful rule is this: **choose the spelling system that fits the document's job**. Language still signals audience. But in technical work, system compatibility now shapes that choice too. --- If you regularly switch between British and American English, [RewriteBar](https://rewritebar.com/) can make that much less tedious. It works across apps on macOS, lets you rewrite selected text in place, and helps you keep spelling, tone, and localization consistent whether you're drafting a client email, editing product copy, or cleaning up technical documentation. ![Portrait of Mathias Michel](https://rewritebar.com/_next/image?url=%2F_next%2Fstatic%2Fimmutable%2Fmedia%2Fmathias.35h56kwevcs7u.jpg&w=256&q=75) About the Author ## Mathias Michel Maker of RewriteBar Mathias is Software Engineer and the maker of RewriteBar. He is building helpful tools to tackle his daily struggles with writing. He therefore built RewriteBar to help him and others to improve their writing. [Twitter](https://twitter.com/m91michel)[LinkedIn](https://www.linkedin.com/in/michel-x-mathias/)[GitHub](https://github.com/m91michel) More to read [Mastering Articles in Grammar for Better Writing](https://rewritebar.com/articles/articles-in-grammar "Mastering Articles in Grammar for Better Writing") Master articles in grammar with clear rules for definite, indefinite, and zero articles. Learn exceptions, avoid common errors, and practice with AI tools. [Commas in Compound Sentences: A Clear Guide for 2026](https://rewritebar.com/articles/commas-in-compound-sentences "Commas in Compound Sentences: A Clear Guide for 2026") Master commas in compound sentences with this clear guide. Learn the rules, avoid common mistakes, and improve your writing today. [Custom Keyboard Shortcuts Mac: A Practical Guide](https://rewritebar.com/articles/custom-keyboard-shortcuts-mac "Custom Keyboard Shortcuts Mac: A Practical Guide") Learn to set custom keyboard shortcuts Mac with our practical guide—covering system settings, Quick Actions, third-party tools, and conflict fixes. Tags [Grammar](https://rewritebar.com/articles/tags/grammar)[Writing Tips](https://rewritebar.com/articles/tags/writing-tips)[Common Mistakes](https://rewritebar.com/articles/tags/common-mistakes)[Workplace Writing](https://rewritebar.com/articles/tags/workplace-writing) Written by [![Avatar of Mathias Michel](https://rewritebar.com/_next/image?url=%2F_next%2Fstatic%2Fimmutable%2Fmedia%2Fmathias.35h56kwevcs7u.jpg&w=64&q=75)Mathias Michel](https://rewritebar.com/blog/author/mathias "Posts by Mathias Michel") Published July 20, 2026