Most writers know the moment. You’re reading through a draft, red pen in hand, and you land on a paragraph you actually like. The sentence has rhythm. The image works. But it doesn’t belong here anymore. The scene moved on, the argument tightened, or the piece simply doesn’t need it. You know you should cut it. Your hand doesn’t move.
This hesitation is not laziness and it’s not weak editing instinct. It’s a specific kind of resistance that shows up again and again during revision, and there’s a simple habit that removes most of the pain from it: keeping a cut file.
I’ve spent the last five years working through revisions on client projects, personal essays, and long-form drafts, and the single change that made my editing faster and braver wasn’t a new outlining method or a fancy tool. It was a plain text document sitting next to my draft, catching everything I cut. Once I started using one, I stopped protecting sentences that were only slowing the piece down. I want to walk through why deletion feels so hard, where the “murder your darlings” advice actually comes from, and exactly how to set up a cut file that does real work instead of becoming digital clutter.
Where “Murder Your Darlings” Actually Comes From
Writers repeat this phrase so often that most people assume it belongs to a famous novelist. It doesn’t. The line traces back to Sir Arthur Quiller-Couch, a British writer and critic who delivered a series of lectures at Cambridge in 1914, later published as On the Art of Writing. In one of those lectures, he told students to watch for the moments when they feel especially proud of a phrase, and to treat that pride as a warning sign rather than a compliment.
His actual advice was more specific than the shortened version people quote today. He told writers that whenever they felt an impulse to write a phrase because it sounded beautiful, they should stop, cross it out, and — in his words, paraphrased here rather than quoted directly — kill the passage they loved most, without mercy. The point wasn’t that good writing has to be plain or that pretty sentences are bad. His argument was that writers get attached to language for the wrong reasons. A sentence can be well built and still not serve the piece. When a writer keeps something because it feels clever rather than because it earns its place, the whole draft gets weaker.
Over the following century, the quote got clipped, reworded, and reattributed. William Faulkner is the name most commonly (and incorrectly) linked to it, even though no reliable record shows him saying it. Stephen King used a version of it in his memoir on writing, which likely helped spread the misattribution further. The correction matters here for a practical reason, not a trivia reason: Quiller-Couch wasn’t telling writers to distrust all their best work. He was warning them about a specific trap — falling for a sentence because of how it sounds rather than what it does for the reader. That distinction is the whole reason a cut file works. It gives you a place to put the sentence you’re proud of without pretending the piece needs it.
Why Cutting Feels Like Losing Something You Paid For
There’s a reason deletion feels heavier than it should, and it isn’t really about the words themselves. It’s about how your brain treats effort you’ve already spent.
Behavioral psychology has a name for this: loss aversion. People feel the pain of losing something more sharply than they feel the pleasure of gaining something equal in value. This shows up constantly outside of writing — in why people hold onto a stock that’s losing money, or keep a gym membership they never use, or finish a bad meal because they already paid for it. The sunk cost is gone either way. The brain still resists letting go of it.
Writing triggers the same response. A sentence you wrote at 11 p.m. after three failed attempts feels like it cost something, because it did. Cutting it doesn’t just remove text from a document. It feels like erasing the effort that produced it. That’s why deleting a weak sentence you dashed off in ten seconds is easy, while deleting a strong sentence you fought for is hard, even when the strong sentence is the one hurting your draft.
A cut file works because it changes what deletion actually means. Instead of destroying the sentence, you’re moving it. The words still exist. You can see them any time you open the file. Your brain registers this as relocation, not loss, and that small shift is enough to lower the resistance most writers feel every time they reach for the delete key.
Here’s a short comparison of how the same edit feels with and without a place to put what you remove:
| Situation | Deleting Straight From the Draft | Deleting Into a Cut File |
|---|---|---|
| Emotional response | Feels like losing finished work | Feels like filing it elsewhere |
| Decision speed | Slow, second-guessing | Faster, less hesitation |
| Willingness to cut strong lines | Low | Higher |
| Risk of restoring weak material later | Higher, out of regret | Lower, since it’s saved but out of sight |
| Record of editing choices | None | Built in automatically |
None of this means the cut file is where good sentences go to eventually get used again. That’s actually the part most advice on this topic gets wrong, and I’ll get to it directly further down.
What a Cut File Actually Is
A cut file is nothing more than a plain document — a plain text file, a simple word processor doc, or a note in whatever app you already use — where every cut sentence, paragraph, or scene gets pasted the moment it leaves your draft. That’s the entire concept. The value isn’t in the tool. It’s in the habit of always having somewhere to put what you remove, so removing something never feels final.
I keep mine dead simple on purpose. No folders, no tagging system, no elaborate structure. The second a cut file becomes its own project to maintain, writers stop using it, which defeats the point.
One File Per Project vs. One Lifetime File
Writers usually land on one of two setups, and both work, depending on how you write.
One file per project means you start a fresh cut file for each piece, document, or manuscript. Everything cut from that specific project lives in that one file, next to the draft it came from.
One lifetime file means you keep a single running document across everything you write, with new cuts added to the bottom (or top) no matter what project they came from.
Here’s how the two compare in practice:
| Feature | Per-Project Cut File | Lifetime Cut File |
|---|---|---|
| Best for | Long projects: books, reports, multi-draft essays | Writers who work on many short pieces |
| Searchability | Easier, since everything relates to one topic | Harder without good dating and labeling |
| File size over time | Stays manageable | Grows large, needs occasional trimming |
| Sense of project history | Strong, shows one piece’s full edit trail | Weak per-project, strong across your career |
| Setup effort | New file each time | Set up once, use forever |
I use a hybrid. Long projects get their own cut file. Shorter, recurring work — blog posts, articles, that kind of writing — goes into one ongoing file split by month. Pick whichever matches how you actually write, not whichever sounds more organized on paper.
What to Write in Each Entry
A cut file only pays off if you can understand your own entries later, and that means adding a small amount of context every time you paste something in. The habit I’ve stuck with for years is short and takes about ten seconds per cut:
- Date of the cut
- The cut text itself, pasted exactly as it appeared in the draft
- One line explaining why it got cut — not a paragraph, just enough to jog your memory
A real entry from one of my own files looks like this:
July 3 — Cut from intro. “The city at night has a way of making you forget what you were worried about that morning.” Cut because the piece isn’t about the city; it’s about the phone call. Nice image, wrong essay.
That one line does two jobs. It stops you from re-reading the cut sentence three weeks later and wondering if you made a mistake, because your past self already explained the decision. And over time, those one-line notes turn into a record of your editing judgment — a pattern you can actually study. If you keep noticing you cut sentences for being “pretty but off-topic,” that’s useful information about a habit worth watching for earlier in your first drafts.
A Simple Cut File Template
If you want a starting structure rather than building one from scratch, this format works for most writers:
[Date] — Cut from [section/chapter/paragraph]
Text: [paste the exact cut passage]
Reason: [one line, honest, no essay]
Keep every entry to those three parts. Anything more elaborate turns the cut file into a second writing project, and that’s exactly the kind of friction that makes people abandon the habit within a week.
Does Anything in a Cut File Ever Get Reused?
Here’s the part most advice on this topic skips, probably because it’s a less satisfying answer than “yes, and here’s how to recycle your best lines.”
The honest truth: almost nothing in a cut file gets reused. I’ve kept cut files for years, and if I’m being accurate about it, the percentage of cut material that ever makes it back into a finished piece is small — closer to the rare exception than a regular event. Most cuts stay cut. The sentence you loved and moved into the file will likely sit there, untouched, for the rest of that file’s life.
That might sound like the cut file was pointless. It isn’t, and here’s why: the value of a cut file was never about salvage. It’s about permission. Knowing you have somewhere to put a sentence — even if you never open that file again — is what lets you cut it in the first place. The safety net doesn’t need to catch you. It just needs to exist so you’re willing to jump.
This distinction matters because writers who set up a cut file expecting it to become a personal stockpile of reusable material often get discouraged when they check back and find they never draw from it. That’s not a sign the system failed. That’s the system working exactly as intended. The cut file did its job the moment it let you delete a sentence without a fight. What happens to that sentence afterward is beside the point.
A small number of exceptions do happen. Sometimes a scene cut from one project turns out to fit a completely different piece months later. Sometimes a phrase you cut for being too much for an intro works better as a closing line somewhere else. These moments happen. They’re just rare enough that you shouldn’t build your whole reason for keeping a cut file around them.
How a Cut File Changes the Way You Revise
Once cutting stops feeling like loss, something else shifts too: the boldness of your edits. Writers without a cut file tend to make small, cautious trims — a word here, a clause there — because each cut carries the full emotional weight of permanent loss. Writers with a cut file tend to make bigger structural cuts, because the stakes of any single deletion drop.
A few patterns I’ve noticed in my own revisions since adopting this habit:
- I cut whole paragraphs faster, instead of just trimming sentences inside them.
- I catch myself keeping material out of attachment less often, because the attachment has somewhere safe to go.
- My second drafts get shorter and tighter, since fear of deletion stops padding my editing decisions.
- I revisit fewer “maybe I shouldn’t have cut that” moments, because the note in the cut file already explains the choice.
This isn’t about cutting more for its own sake. Plenty of sentences deserve to stay exactly where they are. The point is that the decision to cut or keep should come from whether the sentence serves the piece, not from how much it would hurt to lose it. A cut file removes the second factor from the equation, which leaves you free to judge based on the first.
Common Mistakes Writers Make With Cut Files
A cut file can fail just as easily as it can help, usually for one of these reasons:
- Making the entry process too long. If pasting a cut sentence with notes takes two minutes instead of ten seconds, writers stop bothering after the first few cuts.
- Treating it as a to-do list. A cut file isn’t a reminder to bring material back. Adding that expectation defeats the psychological trick that makes cutting easier.
- Never dating entries. Without dates, a lifetime cut file turns into an unsorted pile that’s impossible to search or make sense of later.
- Reopening it mid-draft. Checking the cut file while you’re still deep in a revision session can pull you back toward material you already decided to remove. Save the review, if you do one at all, for after the draft is finished.
- Skipping the reason line. The one-line “why” is what turns a pile of scraps into a useful record. Without it, you’re just staring at old sentences with no context for why they’re there.
Troubleshooting a Cut File That Isn’t Working
My cut file is getting huge and I never look at it. Is that a problem? Not really, as long as it’s still doing its job during revision. The size of the file matters far less than whether it made cutting easier in the moment. If you want to trim it, delete anything older than a year that you’ve never once revisited.
Should I cut file dialogue and structural changes, or only sentences? Anything, including full scenes, cut paragraphs, or entire sections. The format works the same regardless of size. Larger cuts benefit even more from the reason line, since it’s easier to forget why a whole scene got pulled than why one sentence did.
What if I keep going back to restore things from the file? A little of that is normal early on. If it becomes frequent, it might mean you’re cutting too fast without enough confidence in the decision, rather than a problem with the cut file itself. Slow down the first pass and let cuts sit for a day before deciding they’re final.
Does this work for nonfiction and technical writing, not just essays or fiction? Yes. Reports, articles, and documentation all carry the same attachment problem. A well-researched paragraph that no longer fits the structure still feels hard to remove, even in a technical piece with no creative writing involved.
Do I need special software for this? No. A plain document is enough. Anything that adds friction, like a database or a tagging system, works against the habit rather than for it.
Making the Habit Stick
The only way a cut file earns its keep is through repetition. The first few times you use it, the habit will feel unnecessary, because you’ll still hesitate before cutting anyway. That hesitation fades with use, not with theory. After enough revisions where you watched a cut sentence sit safely in another document instead of disappearing, your brain stops treating deletion as loss. That’s the actual goal here — not a growing archive of unused sentences, but a revision process where your hand doesn’t stop over the delete key anymore.
Keep the file open next to your draft. Keep entries short. Don’t expect to reuse most of what goes in it. Let it do the one job it’s actually good at: giving you permission to cut, right when you need it most.
What’s the hardest sentence you’ve ever had to cut from something you wrote, and did you save it anywhere? I’d like to hear how other writers handle this part of revision — drop your experience in the comments.
