If you moved from Windows to Mac and immediately started right-clicking in Finder looking for New Text Document, you probably had a tiny existential crisis. Finder gives you New Folder. Finder gives you Tags. Finder gives you confidence, style, and maybe a preview pane. But a simple New File command? Not by default.
The good news is that macOS absolutely can do this. The less-good news is that Apple prefers a “create the document in an app, then save it” philosophy, which is elegant until you just want a quick blank file in a project folder and do not feel like opening TextEdit, Word, or some other heavyweight app for a document that currently contains exactly nothing.
In this guide, you’ll learn how to create new files from the macOS right-click context menu using built-in tools like Automator and Shortcuts, plus a third-party option if you want a polished template-based setup. I’ll also show you what works best, what the limitations are, and how to keep the whole thing from turning into a weird little automation science fair project.
Why macOS Doesn’t Show a Built-In “New File” Option in Finder
Out of the box, Finder is designed to create folders, not generic blank files. That is why the built-in shortcut you already have is Shift-Command-N for a new folder, not a new document. Apple expects most files to begin life inside an app such as TextEdit, Pages, Numbers, Word, or your code editor, then get saved into Finder afterward.
That approach makes sense for rich documents, but it is not always practical. If you are setting up a project structure, creating placeholder Markdown files, dropping in README documents, or spinning up shell scripts, a right-click New File option is faster and more natural.
That is exactly where Quick Actions, AppleScript, and Finder extensions come in. With a little setup, you can make Finder behave a lot more like you expect.
Method 1: Create a “New File” Right-Click Option With Automator
This is the classic built-in workaround, and it is still one of the best. You use Automator to create a Quick Action that runs a tiny AppleScript. When you trigger it from Finder, macOS creates a blank file in the current folder and highlights it so you can rename it immediately. It is delightfully efficient once it is set up.
What this method is best for
- Creating blank
.txt,.md, or other simple files - People who want a built-in solution with no extra app
- Users comfortable spending five minutes setting it up once
How to build the Quick Action
- Open Automator.
- Choose File > New.
- Select Quick Action.
- Set the workflow to receive no input in Finder.
- From the library, add Run AppleScript.
- Replace the default script with this one:
- Save the Quick Action with a clear name, such as New Text File.
That script tells Finder to create a new file in the front Finder window’s current folder. The select txt line is the secret sauce because it highlights the new file right away, so you can hit Return and rename it before your brain wanders off to check email.
How to use it
Open a Finder window, go to the folder where you want the file, then right-click an item in that folder and choose Quick Actions > New Text File. macOS will create the file and select it instantly.
If the action does not appear, go to your Mac’s extension settings and make sure Finder Quick Actions are enabled. This is the part where macOS politely pretends it trusts you while also hiding your useful automation behind two settings panels and a shrug.
How to customize the file type
You are not limited to plain text. You can change the filename inside the script to create other starter files:
untitled.mdfor Markdownscript.shfor a shell scriptnotes.jsonfor a JSON stubdraft.htmlfor a web page starter
One smart move is enabling Show all filename extensions in Finder settings. That way you can actually see whether you created .txt, .md, or something accidentally cursed like .txt.txt.
Method 2: Use the Shortcuts App for a More Modern Setup
If Automator feels like a time capsule from an era when brushed metal interfaces roamed the earth, there is a more modern route: Shortcuts. Apple now lets you run shortcuts as Finder Quick Actions, and you can even use AppleScript inside a shortcut when you need Finder-specific behavior.
This method feels cleaner if you already use Shortcuts on your Mac, iPhone, or iPad. It also fits better with the direction Apple has been moving in, since Automator workflows can be brought into Shortcuts.
How to create a Shortcut-based “New File” action
- Open the Shortcuts app.
- Create a new shortcut.
- Add the action Run AppleScript.
- Paste in this script:
- Name the shortcut something obvious, like New File.
- Open the shortcut details and enable Use as Quick Action.
- Then go to System Settings > Privacy & Security > Extensions > Finder and turn it on.
After that, you can trigger it from Finder’s Quick Actions menu. It does the same job as the Automator version, but it lives in Apple’s newer automation system.
Why this method is appealing
- It fits into the current Shortcuts ecosystem
- It is easier to manage if you already automate your Mac
- You can eventually expand it into a bigger workflow
For example, instead of creating just one blank file, you could build a shortcut that creates a whole starter pack: a README, a notes file, a drafts folder, and maybe a placeholder screenshot folder for the chaos you know is coming.
Method 3: Use a Finder Extension App if You Want Templates
If your dream setup is not just “make one empty text file,” but rather “right-click and create a Word document, Pages file, spreadsheet, Markdown file, Python script, or custom template,” then a third-party Finder extension is the most practical option.
Apps like New File Menu are built specifically for this. They can add a real Finder context-menu item, support many built-in templates, and even let you create custom templates. That means you can right-click and create the kind of file you actually use instead of endlessly creating blank text files and converting them later.
Who should use a third-party app
- People who want a polished right-click menu without scripting
- Users who need multiple file types, not just text files
- Anyone working with repeatable templates for projects or office documents
The tradeoff
The upside is convenience. The downside is that you are relying on another app and its Finder extension. For many users, that is still worth it. If you create documents all day long, a proper template menu is less “extra software” and more “saving your sanity in small, repeated doses.”
Which Method Should You Choose?
Choose Automator if…
You want a free built-in solution and mainly need plain files like text, Markdown, or scripts.
Choose Shortcuts if…
You prefer Apple’s newer automation tools and may expand the action later.
Choose a Finder extension app if…
You want a true “New File” menu with templates, document variety, and less tinkering.
For most people, the sweet spot is simple: use Automator or Shortcuts for blank file creation, and use a template app if your workflow involves richer file types.
Tips to Make Your Right-Click File Creation Workflow Better
1. Show file extensions
If you are creating files from scripts, visible extensions matter. It is much easier to spot whether you just made readme.md or a mystery file that only pretends to be helpful.
2. Use descriptive default names
Instead of untitled.txt, consider names like README.md, draft.txt, or notes.txt. You can always rename them, but a smarter default reduces friction.
3. Create separate actions for separate jobs
You do not need one magical button that does everything. It is often better to have a few focused actions, such as:
- New Text File
- New Markdown File
- New Shell Script
- New HTML File
4. Use templates for richer documents
If you frequently create meeting notes, invoices, article drafts, or project briefs, a template-based solution is far better than generating blank files and doing the same setup work over and over.
5. Keep Finder extensions tidy
If your right-click menu starts looking like the junk drawer of a moderately disorganized adult, go into Finder extensions and disable what you do not use. Cleaner menus are faster menus.
Troubleshooting: Why Your “New File” Option Might Not Show Up
If your shiny new Quick Action is nowhere to be found, check these common issues:
- The action is not enabled in Finder extensions. Go to your extension settings and turn it on.
- You are clicking in the wrong place. Some workflows appear when you right-click a file or folder item, not always a blank area.
- The script expects an open Finder window. If Finder has no front window, the AppleScript can fail.
- You saved the wrong workflow type. It should be a Quick Action, not a random automation artifact from 2012.
- You cannot create files in that location. Some folders, volumes, or cloud locations may have restrictions.
If you used Automator and later want to remove the action entirely, delete the saved workflow from your Services folder or disable it in Finder extensions. That is much easier than pretending you will “maybe use it again someday” while it keeps haunting your menu forever.
Is This Better Than Just Using TextEdit or Terminal?
Sometimes, yes. Sometimes, no. If you want a formatted document with actual content, opening an app first still makes sense. But if you are building a folder structure, making placeholders, or dropping in quick starter files, the right-click method is faster.
Terminal is also a valid option. You can create files with shell commands, and power users have been doing that for ages. But for many people, Finder is where file management happens. Being able to right-click and create a new file there simply feels more natural.
That is the real value of this setup: not raw technical power, but reducing the number of tiny interruptions between “I need a file here” and “the file now exists.” Good automation is not flashy. Good automation quietly removes annoying steps before they have a chance to annoy you.
Real-World Experience: What It’s Like to Use a New File Shortcut Every Day on a Mac
Once you add a working New File option to Finder, it starts out feeling like a small quality-of-life tweak. Then, after a week or two, it becomes one of those features you miss immediately on every Mac that does not have it. That is because the benefit is not dramatic in one giant moment. It is cumulative. It saves a few seconds here, a click there, an app launch somewhere else, and suddenly your file workflow feels less fussy.
In day-to-day use, the biggest improvement shows up when you are organizing projects. Say you are building a website folder and want a quick index.html, styles.css, and notes.md. Without a Finder shortcut, you bounce between apps or duplicate old files like some kind of digital raccoon. With a context-menu action, you stay in the folder, create what you need, rename it, and move on. The process feels cleaner because it all happens where the files actually live.
It is also surprisingly helpful for writing. If you keep article drafts, outlines, research notes, or plain-text reminders in Finder, creating a new file from the current folder feels a lot more intentional than opening an editor first and then hunting for the correct save location later. You are starting from the destination instead of working backward to it. That sounds minor, but it reduces those little mistakes where a file gets saved to Downloads, Desktop, or some other digital Bermuda Triangle.
Another place this setup shines is in technical work. Developers, tinkerers, and automation fans often need empty files just to establish structure: config files, README files, placeholder scripts, or tiny test documents. A right-click action is faster than launching Terminal if all you want is the file itself, not a whole command-line session. It feels less like “I am performing an operation” and more like “I am just making a file,” which is exactly the point.
There are, of course, limitations. The built-in script approach is best for blank files, not fully formatted Word or Pages documents. If your workflow depends on rich templates, the barebones AppleScript method will start to feel a little too barebones. That is usually the point where a template-based Finder extension becomes worth it. The good news is that macOS gives you enough flexibility to start simple and grow into something more advanced if needed.
The funniest part is how quickly this starts to feel like something Apple should have included all along. New Folder is already there. Quick Actions are already there. Extensions are already there. Finder is already halfway to the party; it just forgot to bring the actual file. Once you patch that gap, the whole experience feels more complete. Not revolutionary. Not magical. Just sensibly better.
And honestly, that is the sweet spot for Mac productivity tweaks. The best ones do not scream for attention. They quietly remove one annoying step from a task you repeat over and over. Add enough of those improvements together, and your Mac starts feeling less like a system you have to negotiate with and more like a workspace that finally understands the assignment.
Conclusion
If you want to create new files from the macOS right-click context menu, you absolutely can. Finder does not ship with a built-in New File command, but you can add one using Automator, build a more modern version with Shortcuts, or install a Finder extension app if you want templates and more file types.
For quick blank files, the built-in AppleScript approach is the best place to start. It is lightweight, fast, and surprisingly satisfying once it works. For more advanced workflows, Shortcuts and third-party template tools give you room to grow. Either way, the result is the same: fewer steps, less friction, and a Finder workflow that finally stops acting like new files are somebody else’s problem.
