How to Disable JavaScript on an Android Phone or Tablet

JavaScript is enabled by default in Chrome for Android and Samsung Internet because most modern sites require it. Disabling it is useful for deliberate testing and troubleshooting, but it is not a general guarantee of privacy, security, battery savings, or accessibility. For privacy, prefer the browser's documented tracking protections; for accessibility, test the actual page with assistive technology.

This guide covers Chrome for Android (the default browser on most Android phones and tablets) and Samsung Internet (the default on Galaxy devices, and the second most-used Android browser worldwide), plus quick notes for Firefox, Brave, and Opera on Android. All instructions reflect Android 14 and 15 in 2026.

Disable JavaScript in Chrome for Android

1. Open the Chrome app on your Android phone or tablet.
2. Tap the three-dot menu in the top-right corner of the screen.
3. Tap Settings near the bottom of the menu.
4. Scroll down and tap Site settings.
5. Tap JavaScript.
6. Toggle the switch to off. The label will change from "Sites can use JavaScript" to Sites can't use JavaScript.
7. Reload any tabs you already had open so the change takes effect.

Menu path: in Chrome for Android, use Settings → Site settings → JavaScript. This guide does not present the desktop internal settings URL as an Android shortcut without verification on a named Chrome build.

On older Chrome versions you may see the toggle labeled Allowed / Blocked instead of "Sites can use JavaScript" / "Sites can't use JavaScript". The behavior is identical - blocked means JavaScript is off site-wide.

Check for a per-site JavaScript exception

Current Chrome help for Android documents the global menu path, but this guide has not verified a consistent per-site exception interface across current Android builds. Do not assume the desktop Allow and Block lists are present.

1. Record the exact Chrome and Android versions before changing the setting.
2. Open Settings → Site settings → JavaScript and inspect only the controls visible in that build.
3. If the page explicitly offers an exception control, add the exact site URL (for example, https://mail.example.com), reload the site, and verify the actual behavior.

If no per-site control is shown, this guide does not provide an internal URL or hidden shortcut to create one.

Do not generalize Chrome desktop exception lists or assume that Samsung Internet, Brave, or Opera exposes an identical Android control. Check current vendor documentation for the exact installed build.

Disable JavaScript in Samsung Internet (Galaxy phones)

Samsung Internet ships pre-installed on Galaxy devices and is the second most-used Android browser worldwide, particularly dominant in South Korea, Southeast Asia, and parts of Europe where Galaxy is the default Android brand. Its JavaScript toggle is in a slightly different place than Chrome's:

1. Open Samsung Internet.
2. Tap the menu icon (three horizontal lines) in the bottom-right corner.
3. Tap Settings.
4. Tap Sites and downloads.
5. Tap Site permissions.
6. Tap JavaScript and toggle Allow JavaScript off.

Samsung Internet remembers this setting separately from Chrome - turning JavaScript off in Chrome does not affect Samsung Internet, and vice versa. If you use both browsers on the same Galaxy device, you need to repeat the step in each.

Other Android browsers

• Firefox for Android Release. about:config is not available in Firefox for Android Release, so the desktop javascript.enabled instructions do not work there. Mozilla has exposed about:config in development channels at different times; verify the exact Nightly or Beta build before publishing that path. For supported per-site control, use a maintained extension where available.
• Brave on Android. Current Brave documentation supports site settings and Shields, but the exact menu can change. Verify the installed app version before changing a global permission; use per-site Shields only as a site-specific diagnostic.
• Opera and Opera GX on Android. This guide does not publish the earlier Chrome-derived path because current Opera documentation reviewed here does not verify that exact JavaScript menu. Check the exact app build before proceeding.
• DuckDuckGo browser. Current DuckDuckGo documentation describes Web Tracking Protections but does not document a global JavaScript toggle. The protections are not equivalent to disabling all JavaScript.

Verify JavaScript is actually disabled

Visit any heavily-scripted site you know - a webmail inbox, a streaming service, a social feed, a maps page - and try to interact with it. If the page renders only static content, refuses to log in, or shows a "please enable JavaScript" message, the toggle is off. The home page of enablejavascript.io tells you directly whether JavaScript is running on the device you are currently using - the cleanest way to confirm without triggering ads or trackers on a third-party page.

Why people disable JavaScript on Android

Mobile is where the trade-offs really tip in favor of disabling JavaScript. Five common reasons:

• Battery life and mobile data. JavaScript can contribute to resource use, but the effect varies by page, device, network, and browser protections. Do not promise a battery or data saving without a reproducible measurement for the named scenario.
• Privacy testing. Turning JavaScript off can stop some client-side scripts, but it does not stop server-side logging, IP-based observation, cookies, or every fingerprinting technique. Use the browser's documented tracking protections for everyday privacy and treat JavaScript-off as a bounded diagnostic.
• Security testing. Disabling JavaScript removes one execution path but is not a substitute for browser updates, Safe Browsing, careful permission choices, or operating-system security. Do not describe it as eliminating a class of attacks.
• Web development and mobile QA. Mobile developers and QA engineers regularly turn JavaScript off to verify that a site still serves usable content: that critical text is server-rendered, that primary navigation works, that forms still submit, and that nothing important is gated behind a script that may fail on a 3G connection or in a webview that disables JS for security reasons.
• Accessibility. TalkBack and other Android assistive technologies sometimes work more predictably on static HTML than on heavily scripted single-page applications, where focus management is uneven and screen-reader updates can be missed when content swaps in dynamically.

Heads-up: large parts of the modern web will not work

With JavaScript off, many interactive features can fail, including sign-in flows, video players, infinite scroll, messaging, banking dashboards, and embedded webviews. Some static pages may remain readable, but that depends on how each site is built. Use the global switch temporarily for a defined test, then restore the normal setting.

Troubleshooting

• Toggle is greyed out. If the JavaScript switch in Chrome won't move, you are probably on a managed work profile (Android Enterprise) where an MDM admin has locked browser settings. Check Settings - Accounts to see if a work profile is active, then ask your IT admin to relax the policy.
• The change doesn't take effect on a tab that was already open. Chrome caches loaded pages. Pull down to refresh, or close and reopen the tab.
• Some sites still feel like they are tracking me. Server-side logging and data carried in requests can continue with JavaScript off. Review the browser's documented tracking protections and site permissions; do not treat JavaScript-off as a network-level privacy control.
• I want to disable JavaScript only on a few sites, not globally. Check whether the exact browser build documents a per-site JavaScript permission. Firefox desktop can use a maintained extension such as uBlock Origin or NoScript; do not infer that every Android browser exposes the same control.

Re-enable JavaScript later

Use the documented menu path in reverse. In Chrome: three-dot menu → Settings → Site settings → JavaScript → Sites can use JavaScript. In Samsung Internet, verify the visible labels on the exact app build before publishing or following a path. Firefox for Android Release does not expose about:config; do not use the desktop re-enable path on Release. Reload open tabs after changing a setting.