To stop future jumpscares, turn off the extension's enabled switch. Deselecting every video is not an off switch in version 1.0.0: an empty selection falls back to all videos. Configure the timer while disabled, and check the exact publisher and permissions before installing.
Identify the extension before installing it
This guide covers FNAF Jump Scare, offered by mesajonathan0 in the Chrome Web Store. Its store ID is gfeohnjfehbjlbgadiaemfkifhpmigme. On October 23, 2026, the listing and the package served by Google's update service both identified version 1.0.0; the store listed September 15, 2025 as its update date.
It is a fan-made extension that schedules sudden FNAF video/audio overlays while you browse. It is not an official Five Nights at Freddy's product. Several similarly named GitHub projects and Firefox add-ons exist, so instructions for one should not be applied to another by name alone.
We inspected this exact store package's manifest and JavaScript, and tested a few scheduling functions with mocked browser APIs. We did not install it in a real browser, play its videos, or run a full security audit. No game audio or images are hosted on this page.
Read the requested access
The checked Manifest V3 package requests the following permissions:
| Permission | Relevant behavior in the inspected package |
|---|---|
storage |
Save the enabled state, timing range and selected videos |
alarms |
Schedule the next random event |
tabs and activeTab |
Work with browser tabs; the background code queries highlighted tabs |
scripting |
Inject the content script used to display an overlay |
| HTTP and HTTPS host access | The manifest requests http://*/* and https://*/*; its content script matches <all_urls> |
The website access is broad. A small entertainment extension can still have permission to interact with many pages. Review Chrome's actual permission prompt and the extension's Details before choosing to enable it. A familiar character or a store rating does not narrow that access.
The developer's store disclosure says it does not collect data and works offline. Treat that as the developer's claim, not an independent certification. In the inspected code, preferences use chrome.storage.sync. Chrome's storage documentation explains that this area can synchronize settings when browser sync is enabled. “No developer tracking” and “settings never leave this device” are different statements; we cannot support the latter unconditionally.
Install through the identified store listing
If you decide to use this extension on your own desktop browser, open the exact listing above, check the provider and ID, then use Add to Chrome and review the confirmation. Chrome's extension-management help describes the install and management flow. Work or school policies may prevent installation.
This listing does not require an unofficial CRX download or a random GitHub ZIP. A repository using the words “FNAF jumpscare” is not evidence that it produced this store package. We did not find a verified source-repository link establishing that relationship and do not supply a sideloading recipe.
Chrome's mobile “Add to Desktop” flow is not local installation into the phone's Chrome browser. The configuration steps below concern the desktop Chrome extension. We have not tested other Chromium browsers.
Configure while it is disabled
Open the extension's toolbar popup. The inspected popup code defaults to Disabled when there is no saved enabled value. It exposes minimum and maximum delay fields, six timing presets, video selections and an enabled switch.
SETUP ORDER
- Leave the extension disabled.
- Set a minimum and maximum interval.
- Choose the videos you want in the pool.
- Enable only when you expect sudden audio and visuals.
- Use the enabled switch to stop future events.
The popup disables timing inputs, presets and individual video checkboxes while enabled. Turn it off before editing those settings. The code's default timing range is five minutes to ninety minutes; input validation clamps the minimum to at least ten seconds and limits the maximum to four hours. These are code observations, not a stopwatch test or a guarantee that Chrome will fire an event at an exact time.
Deselecting every video does not turn this version off. Its background selection function falls back to the full video list when the saved selection is empty. Our isolated function test reproduced that fallback, and also confirmed that a single saved selection is respected. Use the enabled switch to stop the extension, rather than an empty selection.
Turn it off or remove it
Use the popup's enabled switch to stop future scheduled events. In the inspected background code, disabling clears the named alarm; our mocked-API test confirmed that path. It does not establish that an already-playing overlay disappears immediately. The content script removes its video overlay when playback ends or errors, and the normal off-switch handler does not send its separate overlay-removal message.
For a browser-level stop, open chrome://extensions, find FNAF Jump Scare, and turn its card off. Refresh an affected page if injected content remains. To uninstall, choose Remove on that card and confirm. Recheck the store ID if more than one similarly named extension is present.
If you want to limit where it can operate, inspect the extension's Details and Chrome's site-access controls. Restricting access can also prevent the overlay from appearing on excluded pages. Do not loosen access on sensitive sites just to troubleshoot an entertainment feature.
If nothing happens
Check that both Chrome's extension card and the popup switch are enabled, at least one intended video is selected, and your timing range is the one you expected. A newly scheduled random event does not necessarily occur as soon as the minimum interval passes. Internal browser pages such as chrome://extensions restrict extension injection; they are not a useful page on which to expect a jumpscare.
If the controls appear locked, disable the popup switch before editing. If a change does not affect an already-open tab, refresh a normal website after checking the extension state. Playback can also be affected by browser restrictions. We have not reproduced timing or audio playback in an installed browser and cannot diagnose those outcomes from the package alone.
Firefox results are separate products
Mozilla lists Foxy jumpscare by sonnnnaaaaa, also at version 1.0.0 when checked. Its listing describes a Foxy event with a 1-in-1,000 chance and requests access to data on all websites. It is a different add-on, with a different publisher and behavior; it is not a verified Firefox port of the Chrome extension above.
Likewise, a FNAF browser theme is not necessarily an extension that schedules video. Compare the exact publisher, product type and permissions before following a tutorial. The tested source findings on this page apply only to the identified Chrome package 1.0.0.