HIDDEN CHROME PAGES  What are they? + List ▷ 2020

Despite having been using Google Chrome as our preferred browser, we still do not fully know its features. But to cut with this, here we are going to comment on some other things that you should know about this browser.

We will teach you all those details and hidden 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 improve our browser a lot.

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, that surely if it happens, you will regret.

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

The hidden pages are those that allow us to carry out settings to browser. 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 others.

urls list google chrome

There are other more interesting ways, like typing in the address bar “: // plugins /”And we will be shown 4 special browser plugins and the option to deactivate them, the plugins we are talking about 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 mistaken for hidden pages, but they are actually 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 their beta version.

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

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

experimental functions

Differences

Already understanding what the experimental functions are, we can see their differences. Although if you haven’t noticed them yet, We are going to show you a small summary of their differences:

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

List of all hidden pages of Google Chrome and their functions

Now that you know exactly what Chrome’s hidden pages are and what they are used for, It is 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 active globally.
  • chrome: // appcache-internals – This function shows us information about appcached pages and the space they occupy.
  • chrome: // apps / – From this 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 this we see all the caches that exist in our browser.
  • chrome: // chrome/ – There we will see all the Google information
  • chrome: // chrome-urls– With it we can see the list of secret URLs of Chrome.
  • chrome: // components / – It shows us a list of components that Chrome has, 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 it 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 shows us the usual credits of an application.
  • chrome: // device-log / – Through this address we will see the device records.
  • chrome: // devices / – This shows us a list of all devices such as printers connected with Google Chrome
  • chrome: // discards/ – We can see a list of discarded tabs during the session, these tabs are discarded when the RAM is not enough.
  • chrome: // dns– When prefetching is active, we can enter this address in 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 that we have installed.
  • chrome: // flags– We can see experimental functions 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 integrated in Chrome.
  • chrome: // gcm-internals / – We can see information about Google Cloud Messaging.
  • chrome: // gpu– We can see all the information related to the graphics card, such as hardware acceleration.
  • chrome: // help / – We open the Information page of Google Chrome. Here is the version and the possibility of updating.
  • chrome: // histograms– Browser histograms.
  • chrome: // history– It opens the Chrome History manager 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 invalidation information.
  • chrome: // local-state / – It shows us a list of functions and whether or not they are activated in the local installation.
  • chrome: // media-internals – We see all the multimedia elements that we have reproduced.
  • chrome: // nacl – Shows us information about Chrome’s NaCl plugins (Native Client)
  • chrome: // net-internals – It gives us detailed information about the network including SPDY connections or DNS lookups.
  • chrome: // network-error /– Shows network errors.
  • chrome: // network-errors /– Shows network errors.
  • chrome: // newtab – It opens a new tab for us.
  • chrome: // omnibox – We see everything about the Omnibox function and the possibility of changing some parameters of the navigation bar.
  • chrome: // password-manager-internals / – We see logs of the browser’s built-in password manager.
  • chrome: // plugins – It gives us a list of all the plugins and their status.
  • chrome: // policy – There we see all the policies activated in the browser such as the Password Protection Alert.
  • chrome: // predictors – Gives us a list of terms for autocompletion based on 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 – The settings page opens.
  • chrome: // signin-internals – More information and statistics.
  • chrome: // suggestions / – Suggestions.
  • chrome: // supervised-user-internals /– We see a list of active users and the possibility of testing 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 found the Google Chrome terms of service.
  • chrome: // thumbnails / – It shows us the thumbnails stored for the most visited web pages.
  • chrome: // tracing – By activating the Record option, the browser will start collecting all the data of the activities we have carried out.
  • chrome: // translate-internals / – Information about the translation function integrated 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 find information about the version of Chrome, operating system, JavaScript, Flash, command lines, etc.
  • chrome: // view-http-cache – Cached pages.
  • chrome: // webrtc-internals/ – Create a dump of the PeerConnection.
  • chrome: // webrtc-logs / – WebRTC logs captured.

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

Here are 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 /

If you have any questions, leave them in the comments, we will answer you as soon as possible, and it will surely be of great help to more members of the community. Thank you! 😉

You may be interested:

Rate this post

Leave a Comment