Sharepoint keeps opening old version of file

If SharePoint opens a file that is newer in one place and older in another, check the source of truth first: browser copy, Office desktop cache, or the synced library path. Skip that step, and you can keep editing stale content, overwrite newer changes, and fix the wrong layer. This guide shows how to tell which layer is stale and what to do in each case.

What the symptom means

The problem usually means the browser, the desktop app, and the synced local copy are not reading the same file state. Start by opening the document in SharePoint in the browser and comparing the timestamp with the desktop app before changing anything.

SharePoint version history matters here because the library may already contain the correct file, a previous version, or a restore point with a timestamped revision. A downloaded file, a conflict copy, or a renamed copy can look current on disk while being older than the server copy.

Say your workbook shows the 3:20 p.m. edit in SharePoint, but Excel opens a version from 2:10 p.m. That usually points to a desktop cache or wrong local path, not a missing save on the site.

Likely causes

These causes are ranked from most common to less common. Start with the place that is serving the old copy, then move outward to the sync path and the file itself.

• Browser session state or page cache is stale.
• Office desktop cache still holds a temporary copy.
• OneDrive sync is behind, paused, or producing conflict copies.
• The user opened the wrong file path, a shortcut, or a renamed duplicate.
• The file is checked out, locked, or mid-coauthoring conflict.

Browser shows latest but Excel opens old

If the browser copy is current and Excel is stale, the browser is not the problem. The old file is usually coming from the Office document cache, the recent-files list, or a local synced copy that Excel opened instead of the SharePoint library copy.

1. Open the file in SharePoint in the browser and note the modified time at the top of the document pane.
2. In Excel, choose File > Info and check whether the file path points to OneDrive, a local folder, or the SharePoint library.
3. Close Excel completely, then reopen it from File > Open > SharePoint or from the library in the browser, not from Recent.
4. If the desktop app still opens the stale copy, clear the Office document cache and reopen the file.
5. If only Excel is affected, update Excel through File > Account > Update Options > Update Now.

Excel is often the first app to surface stale cached content because workbook files are frequently reopened from the recent list, autosaved locally, and synced through OneDrive. Word and PowerPoint can do the same thing, but workbook file paths and cached copies tend to reveal the mismatch faster.

How do I clear cached SharePoint files and Office cache?

Clear the browser cache only when the browser itself is stale. If the browser is current and the desktop apps appear to be the only outdated part, clear the Office document cache instead; do not treat those as the same problem. Restart the app after clearing so it loads a fresh server copy.

1. Close Word, Excel, and PowerPoint.
2. Open File Explorer and paste %localappdata%\Microsoft\Office\16.0\OfficeFileCache into the address bar.
3. Delete the contents of that folder, not the parent folders.
4. Open the browser and use Refresh, then sign out and sign back in if the page still shows an older revision.
5. Reopen the file from SharePoint, not from Recent.

Why does SharePoint keep opening an old version of my file?

SharePoint keeps opening an old version when the app that launches the file is pointing at the wrong copy, the wrong cache, or an older revision in the library. Open the document in the browser, confirm the timestamp, and then follow the path that matches the stale layer.

Version history can help you tell whether the server copy is correct. A file with previous versions and timestamped revisions may have the right content already on SharePoint, while the desktop app is still holding a temporary cached copy or a conflict file.

Can OneDrive sync cause SharePoint to show an outdated file?

If the OneDrive sync client is paused, offline, or stuck on a conflict copy, the synced folder may lag behind SharePoint. In that case, the browser can show the latest server copy while File Explorer or Office opens an older local copy.

1. Open the OneDrive cloud icon and check Help & Settings > Sync problems or Settings for paused sync.
2. Check the file status icon: green check, blue arrows, or a red X can point to different sync states.
3. Right-click the library or folder and choose View online to compare the cloud copy with the local file.
4. Look for conflict copies or offline files with similar names.
5. If the library is stale, choose Help & Settings > Resume syncing or Unlink this PC, then set it up again.

Suppose a 12 MB budget workbook shows “synced” on one PC but opens yesterday’s numbers in Excel. That often means the sync client completed the folder state but the workbook itself was opened from a conflict copy or an older local path.

Why only one user sees the old version

If only one user sees the stale file, the issue usually sits on that user’s device, account, or sync path rather than in SharePoint itself. A wrong Microsoft 365 account, a duplicate shortcut, or a local synced copy can make one person read an older file while everyone else sees the latest version.

1. Have the user open the file in the browser and compare the timestamp with the desktop app.
2. In OneDrive, check Settings > Account to confirm the signed-in work or school account.
3. In File Explorer, inspect the full path and confirm it points to the expected SharePoint library.
4. Remove duplicate shortcuts or renamed copies from Quick access and the desktop.
5. Resync the library, then reopen the file from the SharePoint site instead of from Recent.

Why all users see the old version

If everyone sees the old file, the site copy is usually stale, the latest edit was saved to the wrong library, or a checked-out file is blocking the current revision from being published. That is when version history and file location matter most.

1. Open the file in SharePoint and choose Version history.
2. Compare the latest timestamp with the time the edit was supposed to be saved.
3. If the correct revision exists, choose Restore on that version.
4. Check whether the file is checked out or locked by another editor.
5. Verify whether a second copy exists in another folder, site, or library with the same filename.

A common first-timer mistake is editing a file with the same name in a different library path and assuming SharePoint lost the change. In many cases, the browser simply opened the wrong location, and the newer copy sits in a separate folder or site.

Version history and file locks

Version history shows previous versions, timestamped revisions, and the restore option for each saved state. If the browser view is right but the desktop copy is wrong, version history tells you whether to restore a revision or keep searching for the file that was actually edited.

Checked-out files and co-authoring locks can delay when others see a change, especially if one editor has not saved or closed the document. AutoSave helps only when the app is connected to the correct cloud file; it does not fix a stale local cache or an incorrect path.

1. Open the file in SharePoint and select Version history.
2. Read the timestamped list and identify the version that matches the intended content.
3. Choose Restore only if the current copy is wrong and the older revision is the correct one.
4. Check whether the file shows Checked out or another lock state in the library details.
5. If multiple people edited the file at once, review conflict copies before restoring anything.

File version matrix

Still not working?

If the browser, Office cache, and sync path all check out, move to the more invasive fixes and collect details before escalation. Keep the file path, library name, version timestamp, and whether the file is checked out or locked.

1. Sign out of Microsoft 365 in the browser and in Office, then sign back in.
2. Repair Office from Settings > Apps > Installed apps > Microsoft 365 > Modify.
3. In OneDrive, choose Help & Settings > Pause syncing, then Resume syncing, or unlink and set up the library again.
4. If permissions, checkout state, or version history look wrong, send the file path and timestamp to the SharePoint or Microsoft 365 admin.
5. If the issue affects a whole library or site, ask the site owner to check checkout rules, retention, and library version settings.

Prevention is simple: open the file from the SharePoint library entry point, not from a stale desktop shortcut or an old recent-file item. That one habit prevents most wrong-path opens.

Frequently asked questions

How do I force SharePoint to open the latest version of a document?

Open the file in SharePoint in the browser, then choose Open in app only after the browser shows the correct timestamp. If the desktop app still opens old content, clear the Office cache at %localappdata%\Microsoft\Office\16.0\OfficeFileCache and reopen from the library.

Why is Excel opening an old version from SharePoint?

Excel often opens from its recent-file list or a cached local copy, which can lag behind the server version. Use File > Open from the SharePoint library, then check File > Info for the actual file path and clear the Office document cache if the path is stale.

How do I tell if the problem is sync, cache, or version history?

If the browser is current but the desktop app is old, it is usually cache or sync. If everyone sees the same old file, check version history and checkout state. If only one person sees it, look at their OneDrive sync status, account, and local file path first.

Does co-authoring or AutoSave affect which version opens?

Yes, but only when the app is connected to the right cloud file. AutoSave sends changes to the server copy, while co-authoring can delay what others see during simultaneous editing. Neither one fixes a wrong local path, a conflict copy, or a stale Office cache.

How do I restore or find the correct version in SharePoint version history?

Open the document in SharePoint, select Version history, then compare timestamps and file contents. If the right revision is listed, choose Restore. If the revision is missing, check whether the file was saved to another library or site with the same name.

What should I check if the file opens old only in desktop apps but not in the browser?

Check the Office document cache, the app’s recent-file entry, and the full file path. Then reopen from SharePoint in the browser, not from Recent. If the problem remains, update Office and inspect whether OneDrive is syncing a conflict copy or offline file.