JavaScript powers interactive web applications, and cookies store session data that keeps you signed in. Both are enabled by default in Chrome, Firefox, and Edge, but they can be disabled by security software, browser hardening, or Group Policy.
When JavaScript is disabled, web apps show broken layouts, buttons stop working, and pages fail to load content. When cookies are blocked, logins fail and sites can't remember your session.
This tutorial covers enabling JavaScript and cookies in all three browsers through the settings UI, plus enterprise deployment via Group Policy for managed environments. Each browser has a slightly different path, so follow the section for your browser.
Before you start
What you will learn
- You'll learn how to enable JavaScript and cookies in Chrome, Firefox, and Edge, both through the browser settings and via Group Policy for managed devices.
- Many business web applications require JavaScript and cookies to function. When they're disabled, apps break, logins fail, and users can't complete tasks. Enabling them restores full functionality.
Requirements
- Access to the browser settings. For enterprise deployment, Group Policy admin access.
- Standard user (admin for Group Policy)
Good to know
- 5 minutes per browser
Quick answer
In Chrome or Edge, go to Settings > Privacy and security > Site settings and enable JavaScript and Cookies. In Firefox, JavaScript is enabled by default (verify via about:config); set Enhanced Tracking Protection to Standard to allow cookies. Restart the browser after changing settings.
Settings > Privacy and security > Site settings > JavaScript / CookiesStep-by-step tutorial
5 stepsEnable JavaScript in Chrome and Edge
Enable JavaScript in Chrome or Edge.
Chrome/Edge: Settings > Privacy and security > Site settings > JavaScriptIn Chrome, click the three-dot menu > Settings > Privacy and security > Site settings > JavaScript. Select Sites can use JavaScript.
In Edge, click the three-dot menu > Settings > Cookies and site permissions > JavaScript. Toggle it to Allowed.
Both use the Chromium engine, so the process is nearly identical.
You can add specific sites to the 'Allowed' or 'Not allowed' lists for granular control.
Verify JavaScript in Firefox
Verify JavaScript is enabled in Firefox.
Firefox: about:config > javascript.enabledFirefox enables JavaScript by default. To verify, type about:config in the address bar and press Enter. Accept the warning. Search for javascript.enabled and confirm it's set to true.
If it's false, double-click it to toggle it to true.
Firefox removed the JavaScript toggle from the main settings UI. The about:config method is the only built-in way to check it.
Restart the Browser and Verify
Confirm the settings resolved the issue.
Close and reopen the browser to apply all changes. Navigate to the website that was having issues. It should now load fully, run interactive features, and keep you logged in.
For managed environments, deploy these settings via Group Policy using the browser ADMX templates for consistent configuration across all devices.
If a site still doesn't work, check for extensions (NoScript, uBlock Origin) or Group Policy settings overriding your changes.
Verify JavaScript and Cookies Are Working
After enabling JavaScript and cookies, reload the affected website. It should now render fully, run interactive features, and keep you signed in.
If a site still doesn't work, check for browser extensions that block scripts (like NoScript or uBlock Origin) or cookies (privacy extensions). These override the browser's own settings for the sites they target.
In managed environments, Group Policy may enforce settings that override local changes. If the settings appear greyed out or 'managed by your organization,' contact IT.
- Web apps load and function. Logins persist across page loads. Interactive features work.
- The site still shows errors. Check for extensions blocking scripts (NoScript, uBlock) or Group Policy overrides.
- JavaScript and cookies are working.
- An extension or policy is still blocking.
Troubleshooting
Site still broken after enabling settings
Cause: A browser extension like NoScript or uBlock Origin is blocking scripts or cookies for the site.
Disable script-blocking and cookie-blocking extensions, or add the site to their allowlists. Test in an incognito/private window with extensions disabled to isolate the cause.
Settings are greyed out or 'managed by your organization'
Cause: Group Policy or MDM is enforcing JavaScript/cookie settings that override local changes.
Contact your IT administrator. In managed environments, browser settings are controlled via Group Policy (Chrome/Edge ADMX) or Intune. Local users can't override them.
Login fails despite cookies enabled
Cause: The site specifically requires third-party cookies, which are blocked by default.
Add the specific site to the third-party cookie allowlist in the browser's cookie settings rather than enabling third-party cookies globally.
Frequently asked questions
Why do I need JavaScript and cookies enabled?
Web applications rely on JavaScript for interactivity and cookies for sessions. Without them, sites can't run scripts, keep you logged in, or remember preferences, causing broken layouts and login failures.
Should I enable third-party cookies?
Yes, but selectively. First-party cookies are needed for most sites to function. Third-party cookies are increasingly blocked by default for privacy. Enable third-party cookies only for specific sites that require them.
Can I enable these via Group Policy for all users?
Yes. Chrome and Edge use the ADMX templates for enterprise policy. Firefox uses policies.json or its ADMX template. Deploy JavaScript and cookie settings centrally via Group Policy.
Are Chrome and Edge settings the same?
Both use the Chromium engine, so their settings paths and Group Policy templates are similar but branded differently. Edge uses the Microsoft Edge ADMX; Chrome uses the Google Chrome ADMX.
