Skip to content
Step by Step Internet 🌐 Guides for learning to surf the Net

What are all the secret internal Google Chrome pages and how to use them to power the browser? 2022 list

What are all the secret internal Google Chrome pages and how to use them to power the browser? 2020 list

Despite having spent many years using Google Chrome as our preferred browser, we still don’t fully know its features . But to cut with this, here we are going to tell you some other things you should know about this browser.

We will show you all those hidden details and functions that you don’t know about Google Chrome , from what they are, how they work and their differences. The proper use of these can allow us to greatly improve our browser.

If you are the most curious, first read carefully what we leave here, so that you do not run the risk of damaging your Chrome , which surely happens , you’ll be sorry.

What are the hidden pages of the Google Chrome browser and what are they for?

Hidden pages are those that allow us to make browser settings . We can find them within the same browser, just by typing in the address bar “Chrome: // Chrome-urls /” (without quotes) and it will show us a list of more than 70 URLs where we can access any of them to activate or deactivate functions, such as browser data, debugging tools and more.

lista de urls google chrome

There are other more interesting ways, such as typing in the address bar “: // plugins / ” and we will be shown 4 special browser plugins and the option to disable them, the plugins of which We speak are: Flash, Native Client, PDF Viewer, and Widevine Content Decryption Module.

Hidden pages and experimental functions Are they the same thing? Differences

Experimental functions may be confused with hidden pages, but in reality they are different . We could say that the experimental functions are those pages that allow us to access different options or functions that are being tested for the browser, but that have not even been taken to its beta version.

To access the internal functions we write in the address bar “Chrome: // flags /” , and from that we will get access to all the experiments of Google for Chrome , in other words; we can access and activate all the new hidden features for Chrome.

Although when we are going to activate it previously it warns us of the page that our security and privacy may be compromised, make our browser unstable or directly lose the data that we have saved.

funciones experimentales

Differences

Already understanding what experimental functions are, we can see their differences. Although if you have not noticed them yet, we will show you a small summary of their differences:

  • Experimental functions are new functions that can be installed in the browser. Differences than hidden pages, since they are functions that are already in Chrome .
  • Experiments when activated can subject our browser to different privacy risks. Unlike in the hidden pages since being previously installed in the browser , these do not put us at any risk.
  • The modifications made by the hidden pages can be reversible, While many of the modifications made by the experimental functions, may not be .

List of all hidden Google Chrome pages and their functions

Now that you know perfectly what Chrome’s hidden pages are and what they are used for, it’s time for you to know each and every one of them below:

  • chrome: // accessibility – This function shows us information about the accessibility of each of the tabs that are open and if the function is activated globally.
  • chrome: // appcache-internals – This function shows us information about appcached pages and the space they occupy.
  • chrome: // apps / – From Here we can see a list of all installed applications.
  • chrome: // blob-internals / – With this function we can obtain information about Binary Large Objects (blobs).
  • chrome: // bookmarks– This address gives us the opportunity to manage bookmarks
  • chrome: // cache – Through From this we see all the caches that exist in our browser.
  • chrome: // chrome / – There we will see all the information from Google
  • chrome: // chrome-urls – With it we can see the l Chrome secret URLs.
  • chrome: // components / – It shows us a list of components that Chrome counts, and allows us to update them.
  • chrome: // conflicts / – With this address we can see all the modules loaded in the browser from the main process and also includes all the registered modules.
  • chrome: // crashes / – This address shows us a report with detailed specifications of the pages that close the browser.
  • chrome: // credits – This address gives us shows the usual credits of an application.
  • chrome: // device-log / – Through this address we will see the device logs.
  • chrome: // devices / – This shows a list of all devices such as printers connected to Google Chrome
  • chrome: // discards / – We can see a list of tabs As discarded during the session, these tabs are discarded when RAM is not enough.
  • chrome: // dns – When prefetching is active, we can enter this address to the bar and it will show us all the information we need.
  • chrome: // downloads – With this address we can see all the download history that we have made with the browser.
  • >

  • chrome: // extensions – It shows us all the extensions we have installed.
  • chrome: // flags – We can see experimental functions and of all kinds that can be activated or deactivated from this page. It allows us to access experimental functions disabled by default.
  • chrome: // flash – It gives us detailed information about the Flash plugins built into Chrome.
  • chrome: // gcm-internals / – We can see information about Google Cloud Messaging.
  • chrome: // gpu – We can see all related information with the graphics card, such as hardware acceleration.
  • chrome: // help / – We open the Google Chrome Information page. Here is the version and the possibility to update.
  • chrome: // histograms – Browser histograms.
  • chrome: // history – The Chrome History manager opens where we can see all the web pages we have visited and if we want to delete it.
  • chrome: // indexeddb-internals / – We see IndexedDB information for the user profile.
  • chrome: // inspect – It gives us the option to inspect elements, pages or extensions.
  • chrome: // invalidations / – We see information about invalidations.
  • chrome: // local-state / – It shows us a list of functions and if they are or not activated in the local installation.
  • chrome: // media-internals – We see all the multimedia elements that we have reproduced.
  • chrome : // nacl – Shows us information about the Chrome’s NaCl (Native Client) plugins
  • chrome: // net-internals – It gives us detailed network information including SPDY connections or DNS lookups.
  • chrome: // network-error / – Show network errors.
  • chrome: // network-errors / – Show network errors.
  • chrome: // newtab – It opens a new tab.
  • chrome: // omnibox – We see everything about the Omnibox function and the possibility of changing some navigation bar parameters.
  • chrome: // password-manager-internals / – We see records of the browser’s integrated password manager.
  • chrome: // plugins – It gives us a list of all plugins and their status.
  • chrome: // policy – There we see all the policies activated in the browser as the Alert of password protection.
  • chrome: // predictors – It gives us a list of terms for autocomplete b roasted in the past activity.
  • chrome: // print – Page to print.
  • chrome: // profiler – Profile tracking information.
  • chrome: // quota-internals – We see information about the amount of space available for Google Chrome and the active profile.
  • chrome: // serviceworker-internals / – We can see all the Service Workers registered by the browser.
  • chrome: // settings – It opens the settings page.
  • chrome: // signin-internals – More information and statistics.
  • chrome: // suggestions / – Suggestions.
  • chrome: // supervised-user-internals / – We see a list of active users and the ability to test filters by URL.
  • chrome: // sync-internals – Detailed information about the synchronization function is dictated.
  • chrome: // system / – We see everything about the system with system diagnostic data.
  • chrome: // terms – We find the Google Chrome service conditions.
  • chrome: // thumbnails / – We show the thumbnails stored for the most visited web pages.

  • chrome: // tracing – Al activate the Record option, the browser will start to collect all the data of the activities we have done.
  • chrome: // translate-internals / – Information about the integrated translation function in the browser.
  • chrome; // usb-internals – We see the possibility of testing connected USB devices.
  • chrome: // user -actions / – We are shown a list of actions carried out by the user, such as closing tabs.
  • chrome: // version – There we found information about the Chrome version, system operating, JavaScript, Flash, command lines, etc.
  • chrome: // view-http-cache – Cached pages.
  • chrome: // webrtc-internals / – Create a PeerConnection dump.
  • chrome: // webrtc-logs / – Captured WebRTC logs.

These are not all that exist, we can also find others, which Google does not link directly as they can block the browser or close it. Except for quit or restart, the others are for developers to try different browser states.

Next the Chrome URLs:

  • chrome://badcastcrash
  • chrome://crash
  • chrome: / / crashdump
  • chrome: // kill
  • chrome: // hang
  • chrome: // shorthang
  • chrome: // gpuclean
  • chrome: // gpucrash
  • chrome: // gpuhang
  • chrome: // memory-exhaust
  • chrome: // ppapiflashcrash
  • chrome: // ppapiflashhang
  • chrome: // quit /
  • chrome: // restart /
We use cookies in order to give you the best possible experience on our website. By continuing to use this site, you agree to our use of cookies.
Accept