Opening spreadsheets, presentations, or PDF documents in Google Drive only to encounter the error: “Sorry, this file cannot be opened right now. Please check the address and try again” brings cloud collaboration to an abrupt halt. Often accompanied by an option to reload or download a raw local copy, this prompt prevents online viewing and concurrent editing. In Google Drive, file rendering is orchestrated by Google Docs Editors and Google Workspace viewing services, which rely on single sign-on (SSO) OAuth session tokens and secure browser storage partitions. When multiple Google accounts conflict within the same browser profile, third-party cookie blocking isolates Google APIs, or local browser caches store stale document session tokens, Google Drive fails to render the file. This guide outlines how to resolve authentication desynchronisation and restore document access.
What Causes the ‘File Cannot Be Opened Right Now’ Error?
Rendering cloud files requires continuous authentication between Google Drive and Workspace web apps. Common root causes include:
- Multi-Account Session Token Confusion: Having multiple Google accounts logged into the same browser session causing URL account indices (e.g.
/u/0/versus/u/1/) to desynchronise against file permissions. - Third-Party Cookie and Storage Partitioning: Modern browser privacy controls blocking cross-site cookies needed by Google Docs iframe viewports.
- Corrupted Browser Cache and Service Workers: Stale offline Google Drive service workers intercepting fetch requests and serving malformed document manifests.
- Interfering Browser Extensions: Ad blockers, privacy shields, or script blockers preventing Google Workspace telemetry and WebSocket synchronization sockets.
- Temporary Google Server-Side Lockouts: Excessive concurrent access requests on a shared public file triggering short-term rate throttling.
Step 1: Test the Document in an Incognito / Private Window
Testing in an isolated window determines whether browser extensions or stored session caches are causing the failure.
- Open Google Chrome or your default browser.
- Press Ctrl + Shift + N (or Cmd + Shift + N on macOS) to launch an Incognito window.
- Navigate to Google Drive and sign in with the specific Google account that owns or has permission to view the file.
- Attempt to open the problematic file:
- If the file opens without error, the root cause is a corrupt browser cache or an interfering browser extension.
- If the file still refuses to open, verify account access permissions or proceed to network and DNS steps below.
Step 2: Sign Out of Conflicting Secondary Google Accounts
Google Workspace apps frequently misroute access requests when multiple profiles share the same active browser container.
- In your browser, visit any Google service (e.g.
google.comordrive.google.com). - Click your Profile Avatar in the top-right corner.
- Click Sign out of all accounts.
- Close all open browser tabs and relaunch the browser.
- Sign in first with the primary Google account that holds editing or viewing permissions for the target document. The primary account will be assigned index
/u/0/. - Open Google Drive and launch the document.
Step 3: Allow Third-Party Cookies and Site Data for Google Drive
Google Docs and Drive use nested iframes and background workers that require cross-origin storage access.
- In Google Chrome, click the three vertical dots (…) in the top-right corner and select Settings.
- Navigate to Privacy and security > Third-party cookies.
- Scroll down to Allowed to use third-party cookies and click Add.
- Enter
[*.]google.comand check the box for Including third-party cookies on this site, then click Add. - Repeat the process to add
[*.]googleusercontent.com. - Return to Google Drive, refresh the page, and test opening the file.
Step 4: Unregister Corrupted Google Drive Service Workers
Stuck progressive web app (PWA) service workers can intercept file requests and return persistent error screens.
- Navigate to
https://drive.google.comin your browser. - Press F12 (or right-click anywhere and select Inspect) to open Developer Tools.
- Click on the Application tab at the top of Developer Tools.
- In the left sidebar, click Service workers.
- Locate any service workers registered under
drive.google.comand click Unregister. - Next, in the left sidebar, click Storage and click Clear site data.
- Reload Google Drive, sign back in if prompted, and open your document cleanly.
Step 5: Make a Copy or Download as a Workaround
If a collaborative file is temporarily throttled or experiencing server-side lockouts, generating a fresh copy bypasses cached state locks.
- In the main Google Drive file list, locate the problematic file.
- Right-click the file and select Make a copy.
- Google Drive will create a duplicate file named “Copy of [Filename]”.
- Double-click the newly generated copy. Because it receives a fresh document ID and clean server state, it will typically open immediately.
- Alternatively, right-click the file, select Download, and view the document using your local office suite (Excel, Word, or Adobe Acrobat).
Google Drive File Error Troubleshooting Reference
| Observed Behavior | Primary Root Cause | Corrective Action |
|---|---|---|
| Opens in Incognito but fails normally | Extension or cache interference | Disable extensions & clear browser site data |
| Redirects between accounts in URL | Multi-account session conflict | Sign out of all accounts and log in to primary only |
| Blank viewer frame with error message | Third-party cookie partitioning | Add [*.]google.com exception in browser settings |
| “File unavailable” on heavily shared file | Temporary Google bandwidth throttle | Use Make a copy to generate a fresh document ID |
Following these steps eliminates authentication routing errors and restores seamless access to your cloud documents in Google Drive.