Media
5 items
Description
Unlock DevTools on sites that block debugging (e.g. disable-devtool): stop forced reloads, page wipes, and detection. DevTools Unlock restores Chrome DevTools on websites that intentionally block debugging. SINGLE PURPOSE This extension does one thing: on sites you enable, it injects an unlock script at document_start (MAIN world) to neutralize common anti-DevTools detectors (such as disable-devtool and similar custom scripts). That stops typical punishments like forced reloads, blanking the page, or hostile redirects so you can debug normally. WHO IT IS FOR • Front-end developers inspecting pages that ship anti-debug scripts • Security researchers and learners who need Elements / Network / Sources available HOW TO USE 1. After install, unlock is OFF for every site by default. 2. Open the target website, click the toolbar icon, and enable “Enable unlock for this site”. 3. The page reloads once. Cross-origin iframe hosts found on that tab can be unlocked together (useful for embedded players). 4. Open DevTools — the page should stay usable instead of wiping or looping reload. PERMISSIONS • storage — save your local per-hostname whitelist (never uploaded) • scripting — register unlock.js at document_start for enabled hosts only • tabs — read the current tab URL / title needed for the popup toggle and reload • host access (<all_urls>) — you may enable unlock on any site; injection must run before page scripts. Chrome Web Store and similar pages are excluded. PRIVACY No personal data, browsing history, or page content is collected or sent to any server. Settings stay in chrome.storage.local on your device. See the Privacy Policy linked on this listing. NOT FOR Bypassing paywalls, DRM, account gates, or any unlawful use. This tool only restores DevTools availability for legitimate debugging and research.
rating_count is the Chrome Web Store ratings count, not a written-review count.