Shortcut Key to Open a New File: Windows and macOS Guide

Learn universal keyboard shortcuts to instantly open a new file on Windows and macOS, with editor examples, command-line paths, and practical tips for faster document creation.

Shortcuts Lib Team

April 19, 2026·5 min read

Keyboard Shortcuts Save Find Open

New File Shortcut - Shortcuts Lib — Photo by MART PRODUCTION via Pexels

Quick AnswerDefinition

The shortcut key to open a new file is a keyboard combination that launches a fresh document in most apps. On Windows it’s Ctrl+N, on macOS it’s Cmd+N. This universal shortcut speeds drafting across editors, word processors, and IDEs, reducing clicks and keeping your workflow flowing.

The value of a universal 'new file' shortcut

Having a single, reliable shortcut to open a new file accelerates your workflow across environments. In practice, the ability to instantly start a fresh document reduces context switching and keeps focus on content creation. This section explores how Ctrl+N and Cmd+N emerged as de facto standards in editors, word processors, and development environments, and why adopting them improves consistency across tools. We'll look at OS differences, app behavior, and common caveats.

Bash

# macOS/Linux: create a new file from the terminal
touch example.md

PowerShell

# PowerShell: create a new file in the current directory
New-Item -Path . -Name "example.md" -ItemType "file"

BAT

REM Windows CMD: create a new file in the current folder
echo.> example.md

Notes: Most apps respect Ctrl+N / Cmd+N for a new, unnamed document. Some environments open a new tab instead of a new window; others may prompt you to name the file immediately. In all cases, this shortcut is a primary launcher for fresh work streams.

Windows and macOS: Ctrl+N vs Cmd+N

Across Windows and macOS, the same concept is expressed with different keys: Windows uses Ctrl+N, while macOS uses Cmd+N. This difference matters when you switch between devices or collaborate with teammates who use a different platform. The practical result is a near-universal muscle memory: press the appropriate modifier and 'N' to start a new document in most apps. Some editors offer alternative bindings or support both keys depending on the profile.

Bash

# Quick demonstration: open a new file in VS Code from the terminal
code --file-write newfile.txt

PowerShell

# Open a new file in PowerShell with an editor-friendly approach
notepad.exe newfile.txt

BAT

REM Windows-only example: new file via command prompt
copy NUL newfile.txt

Tip: Always verify the binding in a fresh editor session, since some apps override global OS shortcuts with per-application defaults.

Universal verification: testing shortcuts across apps

To ensure consistency, test Ctrl+N and Cmd+N in several apps you use daily: a code editor, a word processor, and the file manager. If a shortcut fails to create a new file, check whether the app uses a different action name (e.g., 'New Untitled File') or overrides the keybinding.

JSON

// Example: VS Code keybindings.json for universal 'new file'
[
  { "key": "ctrl+n", "command": "workbench.action.files.newUntitledFile" },
  { "key": "cmd+n",  "command": "workbench.action.files.newUntitledFile" }
]

YAML

# Editor config sketch: YAML representation of bindings
bindings:
  - keys: [ctrl,n]
    action: new_untitled_file
  - keys: [cmd,n]
    action: new_untitled_file

Why this matters: A well-bounded habit reduces friction and keeps you productive, even when switching between projects or editors.

Editor-agnostic tips and pitfalls

While many editors honor Ctrl+N / Cmd+N, some programs use alternative bindings for specialized workflows. For example, spreadsheet apps may use Ctrl+N to start a new workbook rather than a text file. This is where personalization becomes important: you can often rebind keys in settings or user-made profiles.

JSON

// VS Code example: rebind to ensure identical behavior
{ "key": "ctrl+n", "command": "workbench.action.files.newUntitledFile" }

JSON

// JetBrains IDEs (example style): new file action
{ "keys": ["Ctrl+N"], "action": "NewFile" }

Variations to consider: OS keyboard layouts (US vs UK), language-specific modifiers, and accessibility modes can all impact how a shortcut behaves. If a keyboard combo does not work, try the alternate key combination or launch the editor’s built-in shortcuts reference.

VS Code deep dive: new file command and keybindings

Visual Studio Code offers a consistent path to a new file: the product menu and keyboard shortcuts, plus an editable keybindings JSON. This makes it easy to align VS Code with your other tools while maintaining a single mental model.

Bash

# Create and open a new file via terminal, then switch back to editor
code newfile.md
code --goto newfile.md

JSON

// keybindings.json example for VS Code
[ { "key": "ctrl+n", "command": "workbench.action.files.newUntitledFile" },
  { "key": "cmd+n",  "command": "workbench.action.files.newUntitledFile" }
]

What you gain: consistent shortcuts, faster drafts, and less cognitive load when switching projects.

Notepad++, Word, and JetBrains: different flavors

Notepad++ uses Ctrl+N by default for a new document, while Word has a similar shortcut but with some nuances around templates. JetBrains IDEs map Cmd/Ctrl+N per platform, but you may customize with per-language presets. Understanding these differences helps you stay productive when jumping between apps.

XML

<!-- Notepad++ shortcut mapping (example) -->
<keyboard>
  <KeyAssignment key="N" modifiers="Ctrl" action="NewDocument" />
</keyboard>

JSON

// JetBrains: new file shortcut in Settings | Keymap
{ "name": "New File", "shortcut": ["Ctrl+N"] }

Bottom line: Treat Ctrl+N / Cmd+N as a baseline, then tailor it to each editor to avoid conflicts.

Command-line and automation paths to create new files

Beyond GUI shortcuts, you can create new files from the command line to bootstrap projects quickly. This can complement GUI shortcuts by ensuring a consistent starting point regardless of UI.

Bash

# macOS/Linux: create and touch a new file
touch new_project.txt

PowerShell

# PowerShell: create a new file in the current directory
New-Item -Path . -Name "new_project.txt" -ItemType File

Bash

# Cross-platform approach with Python (creates a file):
python - <<'PY'
open('new_project.md','w').close()
print('Created')
PY

Automation tip: You can script a single command to set up a new file and open it in your preferred editor, improving onboarding for new tasks.

Accessibility considerations: keyboard layouts and screen readers

People using screen readers or non-US keyboard layouts rely on predictable bindings and accessible naming. When possible, standardize on Ctrl+N / Cmd+N and provide visible focus indicators and descriptive labels in menus. Consider offering an alternative binding for users who rely on keyboard navigation.

Bash

# Emit a descriptive label for a new file action (example)
echo "New File: Ctrl+N / Cmd+N" > accessibility/shortcuts.txt

PowerShell

# Simple test script to verify label presence
Select-String -Path shortcuts.txt -Pattern "New File" -CaseSensitive

Guidance: Regularly audit shortcuts for accessibility, ensuring that each common action has visible, discoverable labels.

Best practices and future-proofing your shortcuts

To maximize longevity, keep your shortcuts simple and consistent across environments. Prefer single-letter operands with modifiers (Ctrl/Cmd + N) and avoid creating overloaded shortcuts in the same environment. Document any custom bindings in a central place and review them periodically as tools update.

JSON

// Example: a small mapping doc for your team
{ "platform": "all", "standard": { "new_file": "Ctrl+N / Cmd+N" }, "notes": "Avoid conflicts with Save (Ctrl+S)" }

YAML

# YAML: team bindings reference
standard_bindings:
  new_file: ["Ctrl+N", "Cmd+N"]
  save_file: ["Ctrl+S", "Cmd+S"]

Takeaway: The best shortcut policy is consistency, documentation, and regular review to keep your toolkit robust as software evolves.

Steps

Estimated time: 20-30 minutes

1
Identify target editors
List the editors and apps you use most for document creation. Note the default new-file binding in each one and whether it differs from OS-level shortcuts.
Tip: Record one baseline binding per app to avoid confusion.
2
Verify default bindings
Open a new document in each app to confirm the binding behaves as expected. Note any conflicts with Save or other common actions.
Tip: Check per-app help or shortcuts reference.
3
Practice the primary shortcut
Habitually press Ctrl+N / Cmd+N in all major apps until you can rely on it without looking.
Tip: Practice in 2–3 apps daily for a week.
4
Name and save quickly
After opening a new file, name it and save immediately to avoid data loss.
Tip: Use Save As for first-time naming.
5
Customize if needed
If a key combo clashes with another action, remap to a more intuitive sequence in the settings.
Tip: Keep bindings consistent across platforms.
6
Document your bindings
Create a short reference for your team or project with the agreed shortcuts.
Tip: Share a single source of truth to prevent drift.

Pro Tip: Use the universal shortcut as your starting point when learning new editors.

Warning: Some apps override global OS shortcuts; verify in-app bindings before assuming behavior.

Note: Custom bindings can reduce cognitive load if you standardize them across tools.

Pro Tip: Pair a new file shortcut with a 'Save' shortcut to speed up first-time documentation.

Note: If you work across multiple keyboard layouts, ensure bindings remain consistent.

Prerequisites

Required

Windows 10/11 or macOS 12+ (or newer)
Required
Text editor or IDE active on platform (e.g., VS Code, Notepad, Word, or another editor)
Required
Basic keyboard knowledge (Ctrl/Cmd, N)
Required

Optional

Optional: editor-specific keybindings page or preference panel
Optional
Optional: command-line access (Terminal/PowerShell) for automation examples
Optional
Public documentation or help resources for your tools
Optional

Keyboard Shortcuts

Action	Shortcut
Open new fileWorks in most editors and many apps; may map to 'New Untitled' in some workflows	`Ctrl`+`N`
Open new windowUseful when your editor supports multiple workspaces	`Ctrl`+`⇧`+`N`
Save fileSaves the currently active document	`Ctrl`+`S`
Save AsPrompts for a new name/location	`Ctrl`+`⇧`+`S`
Close current tab/documentDoes not quit the app; closes the active tab or document	`Ctrl`+`W`

Questions & Answers

What is the universal shortcut to open a new file?

The universal shortcut is Ctrl+N on Windows and Cmd+N on macOS in most apps. Some apps may assign a different key; check the app's shortcuts list.

How do I create a new file using the command line?

From the terminal, you can create a new file with commands like touch on macOS/Linux or New-Item/echo on Windows PowerShell, depending on the shell. These commands create the file without opening an editor.

What if the shortcut doesn't work in my editor?

Check for per-app overrides or conflicts with other actions. Review the editor's keybindings or preferences and reset to defaults if needed.

Can I customize a shortcut to open a new file?

Yes. Most editors allow remapping the 'new file' action in settings or keybindings. Pick a consistent binding across your tools.

Is there a shortcut to save a newly created file?

Yes. The common shortcut is Ctrl+S or Cmd+S to save. You may be prompted to name or choose a location on first save in some editors.

Main Points

Use Ctrl+N / Cmd+N to open a new file quickly
Verify bindings in each editor you use
Customize bindings for consistency across tools
Test across OSes to maintain muscle memory
Save immediately after creating a new file

← More in Windows Shortcuts

The value of a universal 'new file' shortcut

Windows and macOS: Ctrl+N vs Cmd+N

Universal verification: testing shortcuts across apps

Editor-agnostic tips and pitfalls

VS Code deep dive: new file command and keybindings

Notepad++, Word, and JetBrains: different flavors

Command-line and automation paths to create new files

Accessibility considerations: keyboard layouts and screen readers

Best practices and future-proofing your shortcuts

Steps

Identify target editors

Verify default bindings

Practice the primary shortcut

Name and save quickly

Customize if needed

Document your bindings

Prerequisites

Keyboard Shortcuts

Questions & Answers

Main Points

Related Articles