Chrome Command Line

Posted : admin On 1/29/2022

The default, we'll provide a command line switch.-dns-log-details-dns-prefetch-disable Enables support to debug printing subsystem.-debug-print Allow initialization of all activex controls. This is only to help website developers test their controls to see if they are compatible in Chrome. On your computer, close all Chrome windows and tabs. Open the Control Panel: Windows 7 & Vista: Click the Start menu Control Panel. Windows 8: Point to the top right of your screen. Click Settings Control Panel.; Click Uninstall a program or Programs and Features.; Double-click Google Chrome.; To delete your profile information, like bookmarks and history, check 'Also delete your browsing data.'

Recently someone installed Chrome browser onto their PC, PC was supposedly locked down, but not for Chrome browser installs.

This was how I removed chrome and restore IE as the default web browser.

To remove Chrome from a command prompt, confirm the following path exists by drilling into it. 39.x.xxxx.xx will vary depending on version of Chrome installed. (You can also verify this path from your registry by searching “chrome”)

Next I needed to open up my registry, again from a command prompt I ran this command to elevate my rights.

You get prompted for a password on the next line.

With Regedit open, drill into the following key paths and rename values for following targets.

Finally even doe IE was set to default browser in internet options, it wasn’t as I could not open URL’s unless IE was already open. So:

From DOS run

The Default programs GUI appears and you should be able to reaffirm IE as default browser from their.


  1. 5 Android

There are command line flags (or 'switches') that Chromium (and Chrome) accept in order to enable particular features or modify otherwise default functionality.

Chrome Command Line

Current switches may be found at

It is important to note that some switches are intended for temporary cases and may break in the future.

Note that if you look at chrome://flags to see if the command line option is active, the state might not be accurately reflected. Check chrome://version for the complete command line used in the current instance.


  1. Exit any running-instance of Chrome.
  2. Right click on your 'Chrome' shortcut.
  3. Choose properties.
  4. At the end of your 'Target:' line add the command line flags. For example:
    • --disable-gpu-vsync
  5. With that example flag, it should look like below (replacing '--disable-gpu-vsync' with any other command line flags you want to use):
    chrome.exe --disable-gpu-vsync
  6. Launch Chrome like normal with the shortcut.


  1. Quit any running instance of Chrome.
  2. Run your favorite Terminal application.
  3. In the terminal, run commands like below (replacing '--remote-debugging-port=9222' with any other command line flags you want to use):
    /Applications/ --remote-debugging-port=9222
    # For Google Chrome you'll need to escape spaces like so:
    /Applications/Google Chrome --remote-debugging-port=9222


  1. Quit any running instance of Chrome.
  2. Run your favorite terminal emulator.
  3. In the terminal, run commands like below (replacing '--remote-debugging-port=9222' with any other command line flags you want to use):
    chromium-browser --remote-debugging-port=9222
    google-chrome --foo --bar=2

V8 Flags

V8 can take a number of flags as well, via Chrome's js-flags flag. For example, this traces V8 optimizations:

Chrome Command Line Flags

chrome.exe --js-flags='--trace-opt --trace-deopt --trace-bailout'

To get a listing of all possible V8 flags:

Browse the V8 wiki for more flags for V8.


Visit 'about:version' to review the flags that are effective in the app.

If you are running on a rooted device or using a debug build of Chromium, then you can set flags like so:

out/Default/bin/chrome_public_apk argv # Show existing flags.
out/Default/bin/content_shell_apk argv --args='--foo --bar' # Set new flags

You can also install, set flags, and launch with a single command:

out/Default/bin/chrome_public_apk run --args='--foo --bar'
out/Default/bin/content_shell_apk run # Clears any existing flags

For production build on a non-rooted device, you need to enable 'Enable command line on non-rooted devices' in chrome://flags, then set command line in /data/local/tmp/chrome-command-line. When doing that, mind that the first command line item should be a '_' (underscore) followed by the ones you actually need. Finally, manually restart Chrome ('Relaunch' from chrome://flags page might no be enough to trigger reading this file). See

ContentShell on Android

There's an alternative method for setting flags with ContentShell that doesn't require building yourself:

  1. Download a LKGR build of Android.
  2. This will include both ChromePublic.apk and ContentShell.apk
  3. Install ContentShell APK to your device.
  4. Run this magic incantation
-a android.intent.action.VIEW
-n org.chromium.content_shell_apk/.ContentShellActivity
--esa commandLineArgs --show-paint-rects,--show-property-changed-rects

This will launch contentshell with the supplied flags. You can apply whatever commandLineArgs you want in that syntax.

Chrome Command Line

Android WebView

Chrome Command Line New Window

This is documented in the chromium tree.

Chrome Command Line Arguments

Chrome OS

Chrome Command Line Arguments

  1. Put the device into dev mode, disable rootfs verification, and bring up a command prompt.
  2. Modify /etc/chrome_dev.conf (read the comments in the file for more details).
  3. Restart the UI via:
    sudo restart ui