Paste Works in Word but Not in a Browser

When paste works in Word but fails in a browser — Chrome, Edge, Firefox, or any web app — the cause is almost never the Windows clipboard. Word clearly has access to the clipboard, so the clipboard itself is healthy. The browser is the variable. The cause is usually one of four things: the browser's per-site clipboard permission is off, a browser extension is intercepting paste, the target site is a custom web editor that handles paste differently, or the browser is running at a different integrity level than the source app.

This guide covers the diagnostic order for browser paste failures in 2026. For related symptoms, see paste works in Notepad but not in Word for the inverse case, cannot paste into an admin window for the UAC case, and the broader Win+V not working on Windows 11: 9 fixes and Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11 guides.

Why browsers handle paste differently

Browsers run web content in a sandbox. The sandbox includes a permission model that controls which browser features a site can use — camera, microphone, location, notifications, and clipboard. Modern browsers gate the clipboard behind a per-site permission, and a site that has not been granted clipboard permission will silently refuse paste in some scenarios.

Browsers also run their own JavaScript paste handlers. Many web apps — Google Docs, Notion, Confluence, Slack web, Gmail compose, custom CRMs — intercept the paste event with JavaScript to reformat content, strip formatting, or insert media. A paste handler that throws an error, or that rejects the pasted format, produces a silent paste failure.

A third factor is the browser's process model. Chrome, Edge, and Firefox run each tab in a separate process. If the source app (where the copy happened) is running at a different integrity level than the browser tab, the OS's UIPI (User Interface Privilege Isolation) blocks the clipboard transfer.

Layer 1: check the per-site clipboard permission

Modern browsers expose a per-site clipboard permission. The default varies by browser and by version, but in 2026 the common defaults are:

• Chrome — clipboard-write is allowed on user gesture (e.g., a click before paste). clipboard-read is allowed on user gesture for HTTPS sites.
• Edge — same model as Chrome (Chromium-based).
• Firefox — clipboard-read prompts the user on first paste attempt for sites that request it.

To check in Chrome or Edge:

1. Click the lock icon (or "tune" icon) in the address bar.
2. Look for Clipboard in the permissions list.
3. If it is set to Block, change it to Allow.
4. Reload the page and re-test paste.

To check in Firefox:

1. Click the lock icon in the address bar.
2. Click Clear cookies and site data if a stale permission is suspected.
3. Alternatively, go to Settings → Privacy & Security → Permissions, and review the clipboard setting if exposed (Firefox's UI changes between versions).

A common breakage: a user accidentally clicks "Block" on a clipboard permission prompt and never sees the prompt again. The site then silently refuses paste. Resetting the permission restores normal behaviour.

Layer 2: test in an incognito or InPrivate window

Browser extensions can intercept paste. Grammarly, password managers, ad blockers, and corporate proxy extensions are common culprits. Testing in an incognito window — where extensions are disabled by default — isolates the question.

To test:

1. Open an incognito (Chrome) or InPrivate (Edge) window.
2. Sign into the same web app.
3. Try the paste.

If paste works in incognito, an extension is the cause. To identify which:

1. In the main browser window, disable all extensions.
2. Re-enable one extension at a time, testing paste after each.
3. When paste breaks, the most recently enabled extension is the culprit.

Common offending extensions:

• Grammarly — intercepts paste to scan incoming text.
• Password manager auto-fill extensions (1Password, Bitwarden, LastPass) — can intercept paste into form fields.
• Ad blockers with element-zapping — occasionally block paste handlers on sites they misclassify.
• Corporate security extensions (Zscaler, Cisco Umbrella) — may monitor clipboard activity on managed devices.

Layer 3: rule out a custom web editor

Many web apps use custom JavaScript editors that handle paste in non-standard ways. The most common are:

• Google Docs — uses a web clipboard that is separate from the OS clipboard. Paste into Google Docs sometimes requires Ctrl+Shift+V (Paste as plain text) or the menu Edit → Paste to work around the web clipboard.
• Notion — has its own paste handling that sometimes strips formatting unexpectedly.
• Confluence — has a rich-text editor that may reject pasted HTML it considers unsafe.
• Custom CRM and ticketing systems — often have paste handlers that reject content from outside the system.

The diagnostic test is to paste into a plain text input on the same site (a search box, a comment field) and see if paste works there. If plain text input works but the rich editor does not, the cause is the editor's paste handler, not the browser or the OS.

The workaround is to use Paste as plain text (Ctrl+Shift+V in most browsers) which bypasses most rich-text paste handlers. If plain text paste also fails, the cause is elsewhere.

For a wider discussion of plain-text paste, see how to paste without formatting on Windows and Ctrl+Shift+V does not work everywhere.

Layer 4: rule out HTTPS context

Browsers restrict clipboard access on non-HTTPS pages. A page served over HTTP (not HTTPS) has reduced clipboard permissions in most modern browsers. Paste via Ctrl+V usually still works, but programmatic clipboard access (e.g., a "Copy to clipboard" button that uses the Clipboard API) does not.

To check:

1. Look at the address bar. If the URL starts with http:// (not https://), the site is non-secure.
2. Try the same site over https:// if available.
3. If only http:// is available, paste may behave inconsistently.

Local development URLs (http://localhost) are typically treated as secure context by browsers, so this layer is rarely the cause for developers testing locally.

Layer 5: rule out a UAC integrity mismatch

If the browser is running at normal integrity level but the source app (where the copy happened) is running elevated (as administrator), UIPI blocks the clipboard transfer. This is the same issue as cannot paste into an admin window, but in reverse: the source is elevated and the target is not.

To check:

1. Open Task Manager (Ctrl+Shift+Esc).
2. Find the browser process and the source app process.
3. Right-click each, choose Properties, and look at the integrity level (or use the Details tab and add the Integrity Level column).

If the source app is elevated and the browser is not, the fix is to run both at the same integrity level — either elevate the browser (not recommended for daily browsing) or run the source app unelevated.

For more on this, see cannot paste into an admin window and dragging out of a clipboard app into an elevated window.

Layer 6: rule out a browser bug or stale profile

If layers 1 through 5 do not resolve the problem, the cause may be a browser bug or a corrupted browser profile. Two quick tests:

1. Try a different browser. If paste works in Edge but not Chrome, the cause is Chrome-specific. If paste fails in all browsers, the cause is OS-level.
2. Create a fresh browser profile. In Chrome or Edge, go to Settings → Profiles → Add profile, create a new profile without extensions or custom settings, and test paste. If paste works in the fresh profile, the original profile is corrupted.

A corrupted profile can be reset (Settings → Reset settings) or replaced by a new profile. Resetting clears extensions, cookies, and site data but preserves bookmarks and history.

Layer 7: rule out an OS-level problem

If paste fails in all browsers but works in Word and Notepad, the cause may be OS-level but browser-specific. Two known causes in 2026:

• A clipboard monitor that targets browser processes. Some antivirus suites monitor browser clipboard activity specifically. See third-party antivirus blocking clipboard access.
• A group policy that restricts browser clipboard access. Corporate-managed devices may have policies that limit browser clipboard permissions. See clipboard history grayed out by organization for the wider enterprise picture.

What does not help

A few commonly suggested fixes do not help when paste fails specifically in a browser:

• Restarting the Windows clipboard service — the service is working because Word can paste.
• Clearing Windows clipboard history — clearing history does not affect the live clipboard.
• Disabling Win+V — Win+V is independent of the browser's paste.
• Reinstalling the browser — sometimes works but is rarely necessary; profile reset is faster and less disruptive.

A short checklist

If only one thing is checked, it should be the per-site clipboard permission (layer 1). If two, add the incognito test (layer 2). If three, add the plain-text-input test for custom editors (layer 3). Most cases resolve in the first three layers. Layer 5 (UAC) is for cases where the source app is elevated.

That limit is unpacked in Ctrl+V Inserts a Letter V.

Related reading

• Cannot Paste Into an Admin Window
• Ctrl+V Inserts a Letter V
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Support — Using the clipboard on Windows — official description of the Win+V history and how the live clipboard interacts with apps
• Mozilla — Clipboard API documentation — MDN reference for the web Clipboard API that browsers expose to sites, including the permission model
• Google Chrome — Permissions API — Chrome developer documentation covering per-site permissions including clipboard
• Mozilla — Web security and the clipboard — MDN reference covering secure-context requirements for clipboard access
• Microsoft Learn — User Interface Privilege Isolation — Windows security documentation covering UIPI, which blocks clipboard transfer across integrity levels

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support