How to Change the Name of a Word Document

Renaming a Word document sounds like the simplest thing in the world — until you realize there are at least four different ways to do it, and the right one depends entirely on where the file lives and what you're trying to accomplish. Here's a clear breakdown of every method, what each one actually does, and the factors that determine which approach makes sense for your situation.

Why Renaming Isn't Always One-Step Simple

Microsoft Word doesn't include a dedicated "rename this file" button inside the application itself — at least not in a straightforward way. That's because a document's filename is a property of the file system, not the document content. Word manages what's inside the file; your operating system (or cloud storage service) manages what the file is called.

This distinction matters more than it might seem, especially when files are stored in the cloud, shared with collaborators, or linked from other documents.

Method 1: Rename Directly in File Explorer (Windows) or Finder (Mac)

The most reliable method for locally stored files is renaming through your operating system.

On Windows:

  1. Close the document in Word first (renaming an open file can cause errors)
  2. Open File Explorer and navigate to the file's location
  3. Right-click the file → select Rename
  4. Type the new name and press Enter

On Mac:

  1. Close the document in Word
  2. Open Finder and locate the file
  3. Click the filename once to select it, then click it again (slowly) to enter edit mode — or right-click → Rename
  4. Type the new name and press Return

This method is clean, direct, and works on any version of Windows or macOS. The .docx extension stays intact as long as you don't delete it manually.

⚠️ One important note: If you have file extensions hidden in your OS settings, the extension won't show up during renaming — which is actually fine, because it won't get accidentally deleted.

Method 2: Use "Save As" Inside Microsoft Word

This is the method most people reach for instinctively, and it works — but it creates a copy with the new name rather than renaming the original.

  1. With the document open, go to File → Save As
  2. Navigate to the destination folder
  3. Change the filename in the text field at the bottom
  4. Click Save

The original file remains at its old name and location. You'll need to manually delete it afterward if you only want one version. For quick renaming purposes, this approach creates unnecessary cleanup work — but it's genuinely useful when you want to create a renamed duplicate (for version control, for example).

Method 3: Rename from the Word Title Bar (Newer Versions)

In Microsoft 365 and recent standalone versions of Word (2019/2021), there's a subtle feature tucked into the title bar at the top of the window.

  1. Click directly on the document name displayed in the title bar at the top center of the Word window
  2. A small rename field may appear, allowing you to type a new name inline
  3. Press Enter to confirm

This feature behaves differently depending on where the file is saved:

  • For OneDrive or SharePoint files, the rename takes effect immediately in the cloud
  • For locally saved files, behavior varies by Word version — some builds apply the rename directly, others prompt a Save As dialog

If you don't see the clickable title bar option, your version of Word may not support it, or the feature may not be enabled for your file type.

Method 4: Rename OneDrive or SharePoint Files Through the Browser 🌐

If your Word document lives in OneDrive, SharePoint, or Microsoft Teams, renaming it through the cloud interface is often the most reliable option — especially for shared files.

  1. Open OneDrive.com or your SharePoint/Teams file library in a browser
  2. Right-click the file (or click the three-dot menu next to it)
  3. Select Rename
  4. Enter the new name and confirm

This approach updates the filename across all synced devices and keeps shared links intact in most cases. It's particularly important for collaboratively edited documents — renaming locally synced files through File Explorer can sometimes cause sync conflicts or broken links for other users.

The Variables That Change Everything

The "best" method isn't universal. Several factors genuinely affect which approach works smoothly:

FactorHow It Affects Renaming
File locationLocal files rename easily via OS; cloud files need cloud-side renaming
Word versionOlder versions lack the title bar rename feature
File sharing statusShared files renamed locally can break collaborator access
OS settingsHidden extensions can complicate File Explorer renaming for less experienced users
Linked filesDocuments linked or embedded in other Office files may break if renamed

When Renaming Can Cause Problems

Most of the time, renaming a Word document is completely harmless. But there are situations where it creates downstream issues:

  • Hyperlinks or bookmarks pointing to the file by name (in other documents or emails) will break
  • Mail merge data sources that reference a specific filename will lose their connection
  • Shared OneDrive links behave differently depending on whether the link was generated before or after renaming — in most cases OneDrive preserves the link, but this isn't guaranteed in all configurations
  • Version history in OneDrive and SharePoint is typically preserved through a rename, but it's worth confirming in your specific setup

A Note on File Extensions

When renaming, the file extension (.docx, .doc, .dotx, etc.) should generally stay unchanged unless you have a specific reason to convert the format. Accidentally deleting the extension can make the file appear as an unknown type to Windows, though the file itself isn't damaged — you can always add the extension back.

Modern Word files use .docx by default. Older .doc files (Word 97–2003 format) can still be renamed the same way; the extension just reflects the internal format, not the filename.


The method that works cleanly for one person — someone with a locally saved file on a personal Windows laptop — may cause sync headaches or access issues for someone working in a shared SharePoint environment. Which approach fits depends on how your files are stored, who else is accessing them, and which version of Word you're running.