The “You are not signed in” error in Google Drive usually appears when your browser’s stored sign-in state is out of sync with Google’s servers, or when an extension or cache is blocking the authentication cookies. The fix is almost always a quick sign-out and sign-in cycle, clearing your browser cache, or disabling a conflicting extension. Below is a full breakdown of why this happens and exactly how to resolve it on any device.
Why Does This Error Occur?
Google Drive relies on a persistent login token stored in your browser’s cookies. When you open Drive, it checks this token against Google’s authentication servers. The error appears when that check fails, even though you believe you are logged in. Common causes include:
- Expired or corrupted cookies: The token has a limited lifetime and can become corrupted after a browser update or crash.
- Multiple Google accounts: If you have several accounts signed in, Drive may be trying to load the wrong profile.
- Browser extensions: Ad blockers, privacy tools, or VPN extensions often strip or block the authentication cookies that Google needs.
- Outdated browser or app: Older versions may not support the latest security protocols Google uses.
- System time incorrect: If your device’s clock is off by more than a few minutes, SSL certificate validation fails, and Google assumes you are not signed in.
How to Fix It in a Desktop Browser (Chrome, Firefox, Edge)
Try these steps in order, testing Drive after each one. Most users resolve the issue at step 2.
- Hard refresh the page: Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to force the browser to reload all resources, ignoring cached files.
- Sign out and sign back in: Go to accounts.google.com, click your profile picture in the top right, and choose Sign out. Then go to drive.google.com and sign in again.
- Clear site data for Google Drive: In Chrome, click the padlock icon next to the URL, then Site settings > Clear data. This removes cookies and cached files for drive.google.com only, without affecting your other logins.
- Disable extensions temporarily: Open your browser’s extension manager (e.g., chrome://extensions), toggle off all extensions, and try Drive again. If it works, re-enable them one by one to find the culprit.
- Check your system date and time: Ensure your device is set to automatic time and timezone. An incorrect clock is a silent but frequent cause of this error.
- Try incognito mode: If Drive works in an incognito window (which disables extensions and uses fresh cookies), the problem is likely an extension or a corrupted cookie in your normal profile.
Fixing It on the Mobile App (Android and iOS)
The mobile Google Drive app can show the same error, usually due to a stale app cache or a background sync issue. Here’s what to do:
- Force close the app: On Android, go to Settings > Apps > Google Drive > Force stop. On iOS, swipe up from the bottom and swipe the Drive card away.
- Clear the app cache (Android only): In the same app settings menu, tap Storage & cache > Clear cache. This does not delete your files.
- Sign out from within the app: Open Drive, tap your profile picture, then tap Manage accounts and remove the account. Re-add it by tapping Add account and signing in.
- Update the app: Check the Play Store or App Store for an update. Google frequently patches authentication bugs.
- Reinstall the app: As a last resort, uninstall and reinstall. You will not lose any files, as they are stored in the cloud.
What to Do If the Error Persists in the Desktop App
Google Drive for Desktop (the sync client) can also throw this error. It typically means the app’s local credentials are out of sync with your Google account.
- Pause and resume syncing: Click the Drive icon in the system tray (Windows) or menu bar (Mac), click the gear icon, and choose Pause syncing. Wait 10 seconds, then Resume syncing.
- Sign out and back in: In the same menu, click Preferences > Settings > Disconnect account. Then launch Drive again and sign in.
- Restart the app completely: Right-click the Drive icon and select Quit. Then reopen it from your Start menu or Applications folder.
- Check your internet connection: The error can appear if Drive cannot reach Google’s servers due to a firewall or proxy. Temporarily disable any VPN or proxy to test.
Why You Should Not Use “Skip” or “Try Again” Repeatedly
When the error appears, some users see a “Skip” button that lets them browse Drive without signing in. This puts you in a limited, anonymous mode where you cannot view your own files or upload anything. Repeatedly clicking “Try Again” without addressing the root cause will not help because the underlying authentication token is still invalid. The only reliable path is to force a fresh login, which is why signing out and clearing cookies is the first recommended fix.
Preventing the Error in the Future
While you cannot fully prevent Google’s authentication quirks, you can reduce the frequency of this error:
- Keep your browser and OS updated: Google regularly changes its security requirements, and outdated software often fails silently.
- Use a single Google account for Drive: Multiple accounts increase the chance of a token mix-up, especially if you use the “Switch account” feature often.
- Whitelist Google domains in your ad blocker: If you use uBlock Origin or similar, add
google.comandgoogleusercontent.comto your whitelist. - Do not clear all cookies manually: If you clear cookies frequently, you will sign out of Google every time. Instead, use the site-specific clear data option.
- Set your system clock to automatic: This prevents SSL validation failures that trigger the error.
Frequently Asked Questions
Why does Google Drive say I’m not signed in when I just logged in?
This usually happens because the login token was stored, but the browser’s cache still holds an old version of the Drive page that references a previous session. A hard refresh (Ctrl+Shift+R) often resolves it. If not, sign out and sign back in to generate a fresh token.
Will clearing my browser cache delete my Google Drive files?
No. Your files are stored on Google’s servers, not in your browser cache. Clearing cache only removes temporary files like images and scripts. Your documents, photos, and folders remain safe in the cloud.
Can a VPN cause the “You are not signed in” error?
Yes. VPNs change your IP address, which can trigger Google’s security checks. Some VPN servers are also flagged as suspicious. If you see the error while using a VPN, try disconnecting and reloading Drive. If it works, switch to a different VPN server or add Google domains to your VPN’s split-tunnel settings.
Why does this error happen on my phone but not on my computer?
Each device has its own authentication token. If your phone’s app has a corrupted cache or an outdated version, it will fail even though your computer’s browser is fine. The fix is to clear the app’s cache and sign out/in on the phone specifically.
Is there a way to fix this without signing out?
Sometimes a simple refresh works, but if the error persists, signing out is the only reliable fix. You can try using a different browser or incognito mode to confirm the issue is with your normal browser profile, but you will eventually need to sign out to restore full access.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Gmail Notifications Not Working? Fixes That Work
- Fix Thumbnails Not Showing on Network Drives in Windows 11
- Stop Skype Auto-Start in Windows: 5 Fixes
- SQL Injection Prevention: Step-by-Step Guide
- Fix Windows PowerShell Popping Up
- Print iMessage or Text Conversations on iPhone & iPad