> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/install-the-chrome-extension/when-the-extension-does-not-load.md).

# When the extension does not load

You clicked Edit in app or Preview and your app opened without the Jimo panel, or with an error. Four causes cover almost every case, in this order.

***

## The four causes

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fsos0zeh6UXrIB6BLr2Sz%2Fn11-extension-causes.png?alt=media&amp;token=0dfebab5-f563-464b-962e-672511c63b70" alt="Decision tree: Chrome, logged in, CSP, real app"><figcaption><p>Check in this order</p></figcaption></figure>

#### 1. You are not in Google Chrome

The extension exists for Chrome only. Edge, Dia, Arc, Brave and other Chromium browsers may install it from the store but do not load it reliably. Open your app in Chrome, with the extension pinned, and try again.

#### 2. Your app is behind a login and the page opened logged out

The extension opens the URL stored on the experience. If that URL redirects to your login page, log in on that tab, then relaunch Edit in app from the dashboard. The guided setup has the same limit: given a private app URL, it cannot read the product and offers to continue without it. That is expected, carry on.

#### 3. A Content Security Policy blocks the script

If your application sends a `Content-Security-Policy` header that restricts `script-src`, `connect-src` or `frame-src`, the browser refuses to load Jimo, extension or snippet alike. The symptom: the panel never appears, and the browser console (F12, Console tab) shows a line starting with "Refused to load" or "blocked by Content Security Policy".

The fix is on your side: add Jimo's domains to the allow-list. The list, per directive, is in [Settings > Installation](/docs/settings/installation.md) and in [CSP and identity verification](/docs/getting-started/install-jimo/csp-and-identity-verification.md). Send it to the person who owns your CSP; this has to be done before Step 4 anyway.

#### 4. The page is a demo or a prototype, not your app

The extension works on any page, so building on a demo site or a Figma prototype export is possible. It is also the best way to end the trial with nothing usable: selectors, URLs and user context all differ from your real product. Build on your own app, logged in as a real user.

## Still nothing

Reload the Get Started page: if step 2 is not checked, Chrome has not registered the extension; remove it and install it again from the [Chrome Web Store](https://chromewebstore.google.com/detail/jimo/koipflmbgiibbkcfccgpocdgifapofje). Then write to us from the chat with the URL you tried and a screenshot of the console.

## Related

* [Install the Chrome extension](/docs/getting-started/install-the-chrome-extension.md)
* [Installation settings](/docs/settings/installation.md)
* [Troubleshooting](/docs/settings/troubleshooting.md), for experiences that do not show once the snippet is installed
