Fix Grammarly Not Working in Google Docs

Grammarly’s sidebar stays gray, underlines vanish, and your Google Doc feels like it’s back in 2009. One minute the AI co-writer is flagging every comma splice; the next, silence.

Most users panic-click the refresh button, but the real fixes are quieter: a toggled setting, a stale cookie, an enterprise policy you didn’t know existed. This guide walks through every layer—browser, extension, account, and document—so you can restore the grammar layer without surrendering to copy-paste workarounds.

Diagnose the Exact Breakpoint: Is It the Extension, the Doc, or the Account?

Open a new incognito window, enable only Grammarly, and load the same document. If underlines appear, the culprit lives in your main profile—likely another extension or a cached policy.

Still nothing? Log in with a different Google account and open a blank doc. If Grammarly wakes up, the issue is tied to the original account’s permissions, not the browser.

Create a minimal test file: one heading, one list, one typo. Large docs with 50k-plus words or intricate tables can exceed Grammarly’s real-time scan limit, giving the false impression of a total outage.

Check the Three Status Icons You Keep Ignoring

The Grammarly icon in the toolbar can show a green dot, a yellow warning triangle, or nothing at all. A green dot that disappears after two seconds signals a partial load—scroll to the bottom of the doc to trigger a fresh scan.

Yellow triangle with “Limited support” means the page uses a feature Grammarly can’t parse, like a third-party code block or an active SmartChip. Remove the block temporarily, then re-insert it after the scan finishes.

No icon? Right-click the extension puzzle piece, pin Grammarly, and refresh. Chrome occasionally unpins extensions during silent updates.

Browser-Level Fixes That Take Under 60 Seconds

Clear site data only for Google Docs: open chrome://settings/siteData, search “docs.google,” and delete the single entry. This forces a fresh permission handshake without nuking your entire cache.

Hardware acceleration clashes with Grammarly’s overlay engine. Disable it at chrome://settings/system, restart, and test. If underlines return, re-enable acceleration and update your GPU drivers—an outdated chipset can selectively break canvas-based extensions.

User-Agent spoofing breaks Grammarly on enterprise machines. If your IT department forces a legacy UA string, install a lightweight switcher extension, set it to Chrome 120, and whitelist docs.google.com.

The Cookie Revive Trick

Sign out of every Google service, then sign back in starting with Gmail. Grammarly’s OAuth scope piggybacks on the same token chain; a stale cookie in one tab can block the extension in another.

While signing out, revoke Grammarly’s access at myaccount.google.com/permissions, then re-grant it. This resets the scoped token without touching your saved passwords.

Extension Conflicts: How to Spot the Silent Killers

Grammarly’s content script runs at “document_end,” the same slot used by ad blockers, password managers, and dark-mode injectors. Open chrome://extensions, enable “Developer mode,” and click “background page” for Grammarly. Look for red console errors naming other extensions—those are the aggressors.

Common offenders: Loom, Evernote Web Clipper, and any extension that rewrites the DOM after load. Temporarily disable them, then re-enable one per reload to isolate the conflict.

If you need both Grammarly and the conflicting extension, open the offending extension’s details and restrict its site access to “On click.” This keeps it dormant on Google Docs.

Manifest V3 Quirks You Can’t Ignore

Grammarly migrated to Manifest V3 in early 2023. The new service worker goes idle after 30 seconds of inactivity, so large docs may look “scanned” while the worker is actually asleep. Scroll or type a word to wake it; if nothing happens, open chrome://serviceworker-internals and verify the worker is “running.”

Corporate devices can push a policy that blocks service-worker persistence. Check chrome://policy for “ExtensionSettings” with “*” : { “runtime_blocked_hosts”: [“*”] }. Ask IT to whitelist “chrome-extension://kbfnbcaeplbcioakkpcpgfkobkghlhen” explicitly.

Google Docs Offline Mode Is a Stealth Saboteur

Offline mode caches the entire document locally and disables real-time cloud features Grammarly needs. Click the circled checkmark in the toolbar; if it says “Working offline,” toggle it off and reload.

Even when online, an orphaned service-worker cache can keep the doc in offline state. Open DevTools → Application → Service Workers, click “Unregister” for docs.google.com, then hard-refresh.

If you must work offline, install Grammarly for Windows/Mac and use the desktop app instead of the extension. The native app bypasses Docs’ offline layer entirely.

Resolve the “Sync Paused” Red Herring

A gray “Sync paused” banner at the top of Docs quietly blocks Grammarly’s cloud API calls. Click your profile picture, re-authenticate, and watch the underlines reappear within five seconds.

Enterprise and EDU Lockouts: When Admin Settings Override You

Google Workspace admins can disable all third-party add-ons domain-wide. Open admin.google.com → Security → Access and data control → API controls, and look for “Google Docs” in the restricted list. If Grammarly appears there, request whitelisting under the “Marketplace apps” tab.

Some universities route Docs through a proxy that strips foreign JavaScript. Run a traceroute to docs.google.com; if the last hop shows your campus proxy, switch to a guest network or VPN.

Compliance mode (HIPAA, FERPA) forces a read-only wrapper that blocks any extension capable of transmitting text. Disable compliance view for non-sensitive documents, or use Grammarly’s desktop app set to “local processing only.”

The SAML Dance

SAML single sign-on can expire mid-session, leaving Grammarly with an invalid token. Hit Ctrl+Shift+R to force a SAML renegotiation; the extension will regain access without a full logout.

Document-Specific Landmines: Tables, Smart Chips, and Code Blocks

Grammarly skips any paragraph that contains a Smart Chip—@ mentions, date chips, or dropdown chips. Convert the chip to plain text (Ctrl+Shift+Y), run the scan, then undo to restore the chip.

Nested tables deeper than three levels trigger an internal safeguard that pauses scanning. Break the table into smaller ones, review the text, then merge them back.

Apps Script code blocks are invisible to Grammarly, but sometimes the extension mis-tags adjacent paragraphs as code. Insert a blank line before and after the block to reset the boundary heuristic.

The 50 000-Word Ceiling

Docs larger than ~50 000 words switch to a reduced DOM renderer that drops non-critical overlays. Split the doc into sections, review each in turn, or use Grammarly Editor’s import feature for the full manuscript.

Account-Level Quirks: Free vs. Premium vs. Teams

Free accounts lose access to advanced suggestions in Docs if document ownership transfers to a Workspace domain with default-deny add-ons. Ask the owner to assign you explicit “Editor” rights rather than “Commenter.”

Premium seats can be silently suspended if the billing card fails—no email is sent. Check https://account.grammarly.com/subscription; a red “Retry payment” banner explains vanished suggestions.

Teams accounts with style-guide overrides can suppress basic grammar alerts. Open the Grammarly sidebar → “Adjust goals” and switch the style guide to “Off” for the current doc.

Cross-Device Mismatch

Grammarly’s suggestion cache syncs across devices. If you dismiss an alert on mobile, it won’t reappear on desktop, making it look like the extension is broken. Scroll to the dismissed phrase and click the small “Undo” arrow to restore the underline.

Mobile and Tablet Edge Cases

On iPad Safari, Grammarly works only in desktop mode. Long-press the refresh icon, request desktop site, then tap the floating G icon to open the full sidebar.

Android keyboards with Grammarly embedded block the extension on Docs. Disable the keyboard’s Grammarly toggle, then use the standalone browser extension.

ChromeOS tablets route Docs through a sandboxed browser layer that strips NPAPI hooks. Install the Grammarly Android app, then open Docs in the web version—dual-layer mode restores functionality.

Force-Kill the Floating Keyboard

If the mobile floating G badge covers the cursor, drag it to the bottom edge until it snaps into “mini mode.” The extension recalculates overlay positions and resumes underlining.

Advanced Console Surgery for Developers

Open DevTools → Console and paste: grammarly.editor.getDocumentInfo(). If the returned object shows “isPartial”: true, the extension aborted mid-scan. Trigger a full rescan with grammarly.editor.rescan().

Look for CORS errors referencing “https://f-log-extension.grammarly.io.” If blocked, your network filters the analytics endpoint, not the core API. Whitelist that subdomain in your firewall; suggestions will return even though telemetry stays muted.

Performance junkies can throttle CPU 4× in DevTools → Performance to reproduce the race condition that causes gray-icon syndrome. If underlines appear under throttle, the issue is timing, not blocking.

Custom User Script Workaround

Install Tampermonkey and add a one-line script that fires window.postMessage({type: 'grammarly.forceReconnect'}, '*') on doc load. This brute-forces a re-handshake when all else fails.

When to Escalate: Submitting a Diagnostic That Gets Fixed

Click the Grammarly icon → “Need help?” → “Report an issue.” Check “Include diagnostic info” and paste the console output you captured earlier. Engineers triage tickets with logs 3× faster than vague “it doesn’t work” reports.

Include a share link to a minimal test doc—no corporate data, just the problematic structure. Public docs let support reproduce the bug without signing NDAs.

If the reply asks for a HAR file, export it while the bug is active; HAR captures only the current network state. Filter the file to “grammarly” domain entries to shrink the 30 MB blob to 200 KB.

The Secret Slack Channel

Grammarly maintains a private Slack channel for enterprise admins. Ask your IT liaison to post the ticket number there; internal engineers often hot-patch whitelist entries within hours.