--- title: "Comma After Which: Rules Made Easy" description: "Master the comma after which easily. Learn restrictive vs. nonrestrictive clauses, 'that' vs. 'which,' and parenthetical usage for perfect grammar." url: "https://rewritebar.com/articles/comma-after-which" --- [Back to Articles](https://rewritebar.com/articles "Back to Articles") May 7, 2026[Auditorial](https://rewritebar.com/blog/category/auditorial "Posts in Auditorial") # Comma After Which: Rules Made Easy Master the comma after which easily. Learn restrictive vs. nonrestrictive clauses, 'that' vs. 'which,' and parenthetical usage for perfect grammar. 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 [Coherence in Writing: A Practical Guide for 2026](https://rewritebar.com/articles/coherence-in-writing "Coherence in Writing: A Practical Guide for 2026") Master coherence in writing with practical strategies, examples, and editing techniques that turn fragmented text into clear arguments. [Common Spelling Errors and How to Stop Making Them](https://rewritebar.com/articles/common-spelling-errors "Common Spelling Errors and How to Stop Making Them") Learn why common spelling errors happen, the patterns behind them, and practical strategies and tools to catch and prevent mistakes in your writing. [Changing Passive to Active Voice That Actually Works](https://rewritebar.com/articles/changing-passive-to-active-voice "Changing Passive to Active Voice That Actually Works") Learn changing passive to active voice with clear steps, real examples, and practical tools. Write with confidence and clarity in any context. Published May 7, 2026 Tags [Grammar](https://rewritebar.com/articles/tags/grammar)[Editing](https://rewritebar.com/articles/tags/editing)[Writing Tips](https://rewritebar.com/articles/tags/writing-tips) ![Comma After Which: Rules Made Easy](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/fe5cf5a5-6c66-43b9-909e-87d441ad7652/comma-after-which-grammar-guide.jpg) You’re writing an email, a product spec, or a report. You get to a sentence with **which**, pause, add a comma, remove it, then wonder whether you’ve just changed the meaning. That hesitation is common for native and non-native speakers alike. In global English markets, a **2022 British Council survey of 5,000 non-native speakers found 62% confuse restrictive and nonrestrictive commas, leading to clarity errors in 25% of business emails**, according to [this summary of comma usage research](https://www.statisticssolutions.com/correct-comma-usage/). That’s not a tiny grammar quirk. It affects how clearly people understand your sentence. The good news is that the rule is learnable. Better still, it becomes intuitive once you stop treating it like punctuation trivia and start seeing it as a meaning problem. ## Why the Comma with 'Which' Matters It's commonly believed the issue is the comma **before** _which_. Often, it is. But the fundamental question is bigger: are you adding extra information, or are you identifying exactly which thing you mean? That choice affects tone, precision, and sometimes legal or technical clarity. A marketer can sound sloppy. A developer can write documentation that leaves room for multiple readings. A student can turn a precise claim into a vague one. ### One comma can change the sentence Compare these: > The users who enabled notifications saw the update. > The users, who enabled notifications, saw the update. The first sentence implies only some users enabled notifications. The second implies all the users did. Same words. Different meaning. ### Why busy professionals get stuck The confusion usually comes from one of three places: - **You’re editing fast:** You hear a pause in your head and add a comma because it “sounds right.” - **You learned a shortcut, not the rule:** Many people were told “put a comma before _which_” without learning when that’s true. - **You write for an international audience:** American and British conventions don’t always line up neatly. > Grammar matters most where the reader can’t ask what you meant. If you remember only one idea at this stage, make it this one: the comma with _which_ is not mainly about breathing or rhythm. It’s about whether the clause is **essential** or **extra**. That distinction does most of the work. ## The Core Rule Restrictive vs Nonrestrictive Clauses A clause with _which_ can either narrow the meaning of the noun or add more detail. Those are two different jobs. ![A visual guide explaining the grammatical rules for using a comma with the word which.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/dafa984b-02e6-47af-a937-0d89ce0fed5a/comma-after-which-grammar-guide.jpg) ### Use the by-the-way test A **nonrestrictive clause** adds side information. Think of it as a “by the way” comment. > My laptop, which is five years old, still runs well. The core message is **My laptop still runs well**. The clause **which is five years old** is extra. Helpful, yes. Necessary, no. That’s why commas set it off. A **restrictive clause** identifies which person or thing you mean. Remove it, and the sentence no longer points clearly to the right noun. > The laptop that has the client files needs to stay with me. Without **that has the client files**, you don’t know which laptop. ### A simple comparison | Clause type | Job | Punctuation | Example | | -------------- | ------------------- | -------------------------------------- | --------------------------------------------------------------- | | Restrictive | Identifies the noun | No comma, usually _that_ in US English | The feature that exports CSV is broken. | | Nonrestrictive | Adds extra detail | Comma before _which_ | The export feature, which needs a redesign, is still available. | This is one reason the rule matters so much in technical writing. In technical documentation, **approximately 70% of “which” usage should be non-restrictive, requiring comma separation, and misuse appears in 35-40% of technical documents reviewed by professional editors**, according to [Purdue OWL’s extended comma guidance](https://owl.purdue.edu/owl/general%5Fwriting/punctuation/commas/extended%5Frules%5Ffor%5Fcommas.html). ### Try removing the clause When you’re unsure, delete the _which_ clause and read the sentence again. - If the sentence still points clearly to the same thing, the clause is probably **nonrestrictive**. - If the sentence becomes unclear or too broad, the clause is probably **restrictive**. Examples: > The onboarding email, which goes out on Monday, needs a new subject line. Still clear without the clause: **The onboarding email needs a new subject line.** > The onboarding email that goes out on Monday needs a new subject line. Now the clause identifies one email among several. ### A related pattern worth knowing If this idea feels familiar, it’s because English uses the same logic with appositives and other interrupting phrases. If you want a close cousin to this rule, see these [appositive sentence examples](https://rewritebar.com/articles/appositive-sentence-examples). The underlying question is the same: is the information essential, or is it supplemental? > **Practical rule:** If the clause feels like “by the way,” use commas. If it feels like “specifically this one,” don’t. Once that clicks, the comma stops feeling arbitrary. ## Choosing Between 'Which' and 'That' Once you can tell **essential** from **extra**, the next question is easier: should you use _which_ or _that_? ![A garden path splits into two directions with signs labelled Which for non-essential and That for essential.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/6b68165e-4fb2-4450-b619-5f910d5f31ab/comma-after-which-grammar-choice.jpg) ### The usual American English pattern In standard American edited prose, the cleanest pattern is this: - **Use _that_ for restrictive clauses** - **Use _which_ for nonrestrictive clauses** So: > The plugin **that** handles image compression needs an update. > The plugin, **which** handles image compression, needs an update. The first identifies one plugin. The second assumes the reader already knows which plugin you mean and adds extra detail about it. This lines up with how many professionals were taught to write in school, especially in academic and business contexts. It also makes sentence editing easier because the word choice itself signals the clause type. ### Why UK English complicates the picture At this juncture, many guides cease their explanation, which often confuses readers. In UK English, _which_ is often used more like _that_ is in US usage. According to [guidance discussing transatlantic comma differences](https://east.iu.edu/student-success/coursework/commas.html), corpus data from the British National Corpus shows **30% fewer commas before “which” than in the Corpus of Contemporary American English**, which highlights a real difference in practice. That means a British writer may produce a sentence an American copy editor would revise. Compare: - **US preference:** The report **that** covers Q4 needs revision. - **Common UK pattern:** The report **which** covers Q4 needs revision. Both may be understood. But if you mix conventions inside one document, the prose starts to feel inconsistent. ### A decision guide for real-world writing If you write for a mostly American audience, this is the safest approach: 1. Use **that** for essential clauses. 2. Use **which** for extra clauses. 3. Put commas around nonrestrictive _which_ clauses. If you write for a British audience, you’ll see more flexibility. Even then, clarity still matters more than loyalty to habit. A quick refresher on clause boundaries can help when these sentences get long. This explainer on [dependent and independent clauses](https://rewritebar.com/articles/dependent-and-independent-clauses) is useful if your sentence starts to sprawl. A short video may also help if you prefer hearing the distinction aloud: ### The practical takeaway If your audience is mixed or global, choose consistency over local flavor unless you have a clear house style. > For international business writing, the American split between _that_ and _which_ often reduces ambiguity because the punctuation and word choice reinforce each other. That doesn’t make British usage wrong. It means you should be conscious of which standard you’re following. ## Advanced Punctuation with 'Which' Clauses This is the part most grammar guides barely touch. You know about the comma **before** _which_. But what about the comma **after** _which_? That second comma appears when a parenthetical interrupter sits inside the _which_ clause. ![A magnifying glass positioned over a mind map diagram focusing on the grammatical usage of which.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/6e00d296-fd73-4f4f-b017-e2e7b27a52c5/comma-after-which-grammar-map.jpg) ### When a comma after which is correct Look at this sentence: > The server, which, in our test environment, failed twice, needs investigation. The commas around **in our test environment** are not random. That phrase interrupts the _which_ clause, so it gets its own pair of commas. Break it apart: - Main sentence: **The server needs investigation.** - Nonrestrictive clause: **which failed twice** - Interrupter inside the clause: **in our test environment** Put them together, and you get: > The server, which, in our test environment, failed twice, needs investigation. That comma after _which_ is correct because it opens the interrupter. ### A reliable way to see it Use this layering method: 1. Write the base sentence. 2. Add the full _which_ clause. 3. Insert the parenthetical phrase inside that clause. 4. Put commas around the inserted phrase. Example: - Base: **The feature is still enabled.** - Add clause: **The feature, which is still enabled, affects exports.** - Insert interrupter: **The feature, which, for legacy accounts, is still enabled, affects exports.** You are not putting a comma after _which_ because _which_ demands it. You are putting it there because the next phrase is parenthetical. > If the words after _which_ could be lifted out as an interruption, they need their own commas. That’s the logic. ### Why checkers sometimes get this wrong This is nuanced enough that software often stumbles. **AI tools like Grammarly misflag 25% of valid post-“which” commas in parenthetical phrases, according to 2025 user benchmarks**, as discussed in [Grammarly’s article on commas before which](https://www.grammarly.com/blog/punctuation-capitalization/comma-before-which/). If you’ve ever had a checker insist a correct sentence was wrong, this is one reason. So trust the structure more than the warning. ### Prepositions and which A second advanced case appears when _which_ follows a preposition. > This is the process by which we approve changes. > The contract under which the team operates expires soon. In these cases, _by which_ and _under which_ are part of the clause itself. You usually don’t add a comma because the phrase is doing identifying work. It’s restrictive. But if the whole clause is extra information, commas can still appear: > The old approval process, under which every request needed manual review, has been retired. ### A quick contrast | Pattern | Example | Why | | ------------------------------------ | --------------------------------------------------------------- | ----------------------------- | | Interrupter after _which_ | The draft, which, to my surprise, passed review, was published. | The interrupter needs commas. | | Preposition + restrictive _which_ | The method by which we test builds has changed. | Clause identifies the method. | | Preposition + nonrestrictive _which_ | The old method, by which we tracked every edit, was slow. | Clause adds extra detail. | If you can see the sentence in layers, these “advanced” cases become mechanical rather than mysterious. ## Common Mistakes and How to Fix Them Most comma errors with _which_ aren’t about ignorance. They happen because the sentence changed during drafting and the punctuation didn’t catch up. ![Two open books on a desk, one with marked text and the other showing corrected sentences.](https://cdnimg.co/d2c6ccca-2b78-4e9b-93c0-0341aaba38e9/65b636b2-8c15-4ac8-a8b3-76fcf20401a1/comma-after-which-grammar-books.jpg) ### Mistake one: using which for essential information without adjusting the sentence Before: > The dashboard which tracks trial users needs a filter. After: > The dashboard **that** tracks trial users needs a filter. If the clause tells us **which dashboard**, it’s essential in standard US English. Use _that_, not a comma before _which_. ### Mistake two: forgetting commas around extra information Before: > Our analytics dashboard which tracks trial users needs a redesign. After: > Our analytics dashboard, **which** tracks trial users, needs a redesign. If your reader already knows which dashboard you mean, the clause is extra. Set it off with commas. ### Mistake three: forgetting the closing comma This is common in long sentences. Before: > The billing page, which was redesigned last quarter now loads faster. After: > The billing page, which was redesigned last quarter, now loads faster. A nonrestrictive clause in the middle of a sentence needs **two** commas, not one. Think of them as matching brackets. > **Editing habit:** When you add one comma to mark extra information, look for the second one immediately. ### Mistake four: adding a comma before that Before: > The setting, that controls exports is hidden. After: > The setting **that** controls exports is hidden. In standard American usage, restrictive _that_ clauses don’t take a comma before _that_. ### Mistake five: mishandling an interrupter after which Before: > The feature, which in beta accounts only is enabled by default, caused confusion. After: > The feature, which, in beta accounts only, is enabled by default, caused confusion. If **in beta accounts only** is interrupting the clause, it needs commas around it. These fixes are small, but they sharpen meaning fast. ## How to Edit and Test Your Sentences When you’re proofreading, don’t ask, “Do I hear a pause?” Ask better questions. ### Use the parentheses test If the _which_ clause could sit naturally inside parentheses, it’s probably nonrestrictive and should be set off with commas. Example: > The release notes, which were updated this morning, are ready. You could write: > The release notes (which were updated this morning) are ready. That’s a strong sign the commas belong. ### Use the read-aloud test carefully Reading aloud still helps, but not because commas are just pauses. Read the sentence once without the clause and once with it. - If the sentence stays complete and clear without the clause, it’s probably extra information. - If removing it makes the noun vague, the clause is probably essential. For broader sentence checks, this guide on [how to check sentence structure](https://rewritebar.com/articles/check-sentence-structure) can help you spot when a punctuation issue is really a structure issue. The best outcome isn’t memorizing a bunch of comma rules. It’s training yourself to see what the clause is doing. Once you can do that, the comma after _which_, the comma before _which_, and even the occasional comma after _which_ in a parenthetical all start to make sense for the same reason. --- If you want help catching these issues while you write, [RewriteBar](https://rewritebar.com/) is a practical option. It works across apps on macOS, lets you review edits side by side, and can help you fix grammar, clarity, and tone without breaking your flow. For people who write emails, specs, posts, and documentation all day, that kind of fast feedback makes tricky rules like comma after which much easier to apply consistently. ![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 [Coherence in Writing: A Practical Guide for 2026](https://rewritebar.com/articles/coherence-in-writing "Coherence in Writing: A Practical Guide for 2026") Master coherence in writing with practical strategies, examples, and editing techniques that turn fragmented text into clear arguments. [Common Spelling Errors and How to Stop Making Them](https://rewritebar.com/articles/common-spelling-errors "Common Spelling Errors and How to Stop Making Them") Learn why common spelling errors happen, the patterns behind them, and practical strategies and tools to catch and prevent mistakes in your writing. [Changing Passive to Active Voice That Actually Works](https://rewritebar.com/articles/changing-passive-to-active-voice "Changing Passive to Active Voice That Actually Works") Learn changing passive to active voice with clear steps, real examples, and practical tools. Write with confidence and clarity in any context. Tags [Grammar](https://rewritebar.com/articles/tags/grammar)[Editing](https://rewritebar.com/articles/tags/editing)[Writing Tips](https://rewritebar.com/articles/tags/writing-tips) 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 May 7, 2026