Recommended Free Tools
When Microsoft Project cannot open a file, first make a copy of the original, move a working copy to a local folder, and open it through File > Open > This PC > Browse. That sequence separates a bad path or permission problem from an unsupported format, a version mismatch, a Project Web App cache failure, or a damaged file. Do not convert, overwrite, or repeatedly resave the only copy until you know which problem you are dealing with.
Start with a safe copy and a local path
Before changing anything, duplicate the file in Windows Explorer. Keep the original read-only if possible and give the copy a clear name such as project-test.mpp. Conversions and backward saves can remove information, so preserving the source is the most important recovery step.
As an Amazon Associate I earn from qualifying purchases.
- Copy the file from its current location to a local folder such as Documents or a temporary folder on the computer running Project.
- Open Project and choose File > Open > This PC > Browse.
- Navigate to the copied file instead of relying on the Recent list, a desktop shortcut, an email attachment, or a synchronized-folder link.
- Check that the file is present, that its extension is visible, and that you have permission to read it. If Windows shows a security or synchronization warning, resolve that first.
If the local copy opens, the file itself is probably usable. The original location may involve a disconnected network share, a cloud-sync conflict, an expired connection, a locked file, or permissions that Project cannot use. Work from the local copy, then restore or resynchronize the file only after you have a known-good version.
If the local copy produces the same message, continue with the format and version checks below. A successful copy operation does not prove that the file is a valid Project document; it only proves that Windows could read bytes from the original location.
#1 Best Overall
Verify that the file format is supported
The standard Microsoft Project plan format is .mpp. The extension must match the file’s actual format; renaming a file from one extension to another does not convert it. Ask the sender which Project product and version created the file, especially when the attachment came from an export or an older archive.
| File type or source | What to know | Action |
|---|---|---|
.mpp |
Standard Project Plan format. | Open it from the Browse dialog. If it fails, investigate version, location, cache, or corruption. |
| Selected older Project formats | Some legacy formats can be opened, depending on the installed Project version. | Identify the creating and receiving versions before saving anything. |
| Project 98 | Unsupported by current Project versions covered by Microsoft’s format guidance. Microsoft states that Project cannot open or save to the Project 98 format. | Ask for an export or a save from a supported Project version, or recover through a system that still supports the format. |
.mpx |
MPX project files are not supported. | Request a supported .mpp copy or another exchange format produced by the original application. |
.mpd or .mdb |
These database-based Project formats are not supported for opening in the current application. | Use the original system to export or save the plan to a supported format. |
| ODBC project format | ODBC project files are explicitly unsupported. | Obtain a supported file rather than changing the extension. |
Do not try random extensions as a repair technique. If a sender calls a file “an MPP” but Windows shows another extension, have the sender confirm the export format. A file packaged in a ZIP, downloaded from a portal, or renamed by an email system may also need to be extracted before Project can use it.
Check the Project version that created the file
Version direction matters. Project 2010, Project 2013, and Project 2016 share a file format, which generally allows those releases to exchange plans. That does not mean every feature behaves identically after editing. Microsoft warns that opening a file created in a later version and saving it in an earlier version can lose data or formatting where the later release has enhanced functionality.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsIdentify both versions
- On the computer that cannot open the file, use File > Account (or the product’s About dialog) to record the installed Project edition and version.
- Ask the file’s author for the exact release that last saved it. “Microsoft Project” alone is not enough; the year and edition determine compatibility.
- Check whether the file was last saved by a desktop Project client or by a Project Web App workflow. A server-managed plan can have a local cache copy that behaves differently from a downloaded file.
Open first, save later
If an earlier client can open a later-version plan, make a copy and inspect it before saving. Saving backward may remove newer custom fields, formulas, calendar exceptions, or formatting. The loss can be silent: the file may open normally while a field, rule, or exception is no longer present. Keep the original in the later format and ask the owner to provide a version compatible with your client when those features matter.
When the file will be edited by several people, agree on one supported Project version or on a controlled exchange format. Do not alternate the same master file between different releases without retaining dated backups.
Distinguish a Project Web App cache problem
Files associated with Project Web App can depend on a local cache for synchronization. Microsoft notes that an error can appear when the cache is almost full. In that situation, a plan may fail to open or synchronize even though the server copy is intact.
Check which copy you are opening
- If you are working offline or recently lost connectivity, determine whether Project is opening a local cached project or attempting to retrieve the server copy.
- Do not delete the only local copy before confirming that the server version is current. Unsynchronized edits may exist only in the cache.
- Check the cache status in Project’s cache settings and note whether pending uploads or downloads are listed.
Free space and adjust the cache
Use Project’s cache-management controls to increase the cache limit, move the cache to a drive with adequate free space, or clean old projects. Clean only projects that are no longer needed locally and that have been confirmed on the server. If synchronization is still pending, allow it to complete or export the work before cleaning.
After changing the cache location or size, restart Project and test the local copy again. A cache adjustment will not repair a damaged .mpp file; it addresses storage and synchronization errors around Project Web App.
Test whether an add-in or startup component is blocking Project
If Project refuses files that should be supported, crashes during opening, or shows inconsistent behavior, isolate the application from add-ins and startup resources with Office Safe Mode.
- Close all Project windows.
- Press Windows key + R, enter
winproj /safe, and press Enter. If that switch is not available in your installation, hold Ctrl while launching Project and accept the Safe Mode prompt. - In Safe Mode, open the local test copy through File > Open > This PC > Browse.
If the file opens only in Safe Mode, an add-in, startup template, or extension is a likely cause. Close Project, disable recently added or updated add-ins one at a time through the Office add-in or COM add-in controls, then restart normally after each change. The exact labels vary by Office edition, so change only one component per test and record the result.
Safe Mode is a diagnostic, not a permanent operating mode. If the same supported file fails in Safe Mode, add-ins are less likely to be responsible. Repair the Office installation using Windows’ installed-app or Programs and Features controls, selecting the available repair option. If a quick repair does not help, use the deeper online repair option when offered, then restart Windows and test the untouched copy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When the file itself may be damaged
After the path, format, version, cache, and application checks, a failure limited to one file points toward corruption or a file-specific defect. There is no guaranteed Project-specific “Open and Repair” command in the Microsoft guidance for this error, so avoid utilities that promise to rebuild an MPP without first preserving the original.
Best Value
Use controlled recovery attempts
- Compare the failing copy with a known-good backup, previous version, or server copy. Record the date of each version.
- Ask the last editor to open the original on the computer and Project version that created it. If it opens there, have that person save a new copy without overwriting the source.
- If only a later Project version can open it, use that version to export or save a compatibility copy, while retaining the later-format original.
- If a server copy exists, verify whether it contains the latest synchronized changes before restoring it.
Do not repeatedly open and save the failing file in different versions. Every save can make a recoverable original harder to compare, and backward saves can remove newer fields or formatting even when no warning appears.
Choose the remedy by symptom
| Observed result | Most useful next step | What the result means |
|---|---|---|
| Local copy opens, network or synced copy does not | Resolve permissions, connectivity, locking, or synchronization; keep the local copy as the working backup. | The path or storage layer is the leading suspect. |
Extension is not .mpp or is an unsupported legacy format |
Request a supported export or a file saved by a compatible Project release. | Renaming the extension will not convert the data. |
| Later-version file opens in an earlier client | Inspect it, then avoid saving backward unless feature loss is acceptable. | Newer fields, formulas, calendar exceptions, or formatting may be discarded. |
| Project Web App reports cache or synchronization errors | Check pending work, increase or relocate the cache, or clean confirmed-safe old projects. | The local cache may be full even when the server plan is healthy. |
| File opens in Safe Mode only | Disable add-ins or startup components and retest normally. | Application extensions are interfering with startup or opening. |
| File fails everywhere after all checks | Recover a known-good backup or ask the creating system to produce a new copy. | Corruption or a file-specific defect remains unresolved. |
Prevent the next “cannot open” incident
- Keep dated backups before major schedule edits, imports, conversions, or version changes.
- Store the master plan in a location with reliable permissions and synchronization, and keep a local recovery copy when traveling or working offline.
- Record the Project version used to create and last save each important plan.
- Before exchanging files across releases, identify whether custom fields, formulas, calendar exceptions, or special formatting must survive.
- For Project Web App, monitor cache capacity and pending synchronization instead of cleaning blindly.
- When sending a plan, use the supported
.mppformat and state the creating Project version in the message.
The practical order is deliberate: preserve the original, test a local copy, verify the extension, compare Project versions, inspect the Project Web App cache when applicable, and then isolate the application in Safe Mode. Only after those checks should you treat the file as potentially corrupt and fall back to a known-good version.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
