Chromium命令行开关列表2
Chromium命令行开关列表
Google Chrome浏览器可以使用很多命令行。 一些更改功能的行为，其他用于调试或试验。 该页面列出了可用的开关，包括其条件和说明。 上一次自动更新发生在2020-08-12。
| Condition | Explanation |
|---|---|
| --force-happiness-tracking-system ⊗ | Force enables the Happiness Tracking System for the device. This ignores user profile check and time limits and shows the notification every time for any type of user. Should be used only for testing. ↪ |
| --force-high-contrast ⊗ | Forces high-contrast mode in native UI drawing, regardless of system settings. Note that this has limited effect on Windows: only Aura colors will be switched to high contrast, not other system colors. ↪ |
| --force-hwid-check-failure-for-test ⊗ | Forces Hardware ID check (happens during OOBE) to fail. Should be used only for testing. ↪ |
| --force-legacy-default-referrer-policy ⊗ | Pins the default referrer policy to the pre-M80 value of no-referrer-when-downgrade. TODO(crbug.com/1016541): After M82, remove when the corresponding enterprise policy has been deleted. ↪ |
| --force-login-manager-in-tests ⊗ | Usually in browser tests the usual login manager bringup is skipped so that tests can change how it's brought up. This flag disables that. ↪ |
| --force-logs-upload-failure ⊗ | Force a logs upload failure to help test the logs upload retry. ↪ |
| --force-max-texture-size ⊗ | Sets the maximum texture size in pixels. ↪ |
| --force-media-resolution-height ⊗ | When present overrides the screen resolution used by CanDisplayType API, instead of using the values obtained from avsettings. ↪ |
| --force-media-resolution-width ⊗ | No description ↪ |
| --force-overlay-fullscreen-video ⊗ | Forces use of hardware overlay for fullscreen video playback. Useful for testing the Android overlay fullscreen functionality on other platforms. ↪ |
| --force-pnacl-subzero ⊗ | Force use of the Subzero as the PNaCl translator instead of LLC. ↪ |
| --force-prefers-reduced-motion ⊗ | Forces whether the user desires reduced motion, regardless of system settings. ↪ |
| --force-presentation-receiver-for-testing ⊗ | This forces pages to be loaded as presentation receivers. Useful for testing behavior specific to presentation receivers. Spec: https://www.w3.org/TR/presentation-api/#interface-presentationreceiver ↪ |
| --force-protected-video-output-buffers[16] ⊗ | Forces protected memory for all output video buffers generated by FuchsiaVideoDecoder, including unencrypted streams. Ignored unless --enable-protected-video-buffers is also specified. ↪ |
| --force-raster-color-profile ⊗ | Force rastering to take place in the specified color profile. Accepted values are the same as for the kForceDisplayColorProfile case above. ↪ |
| --force-recovery-component ⊗ | Force the recovery component, when running an unofficial build. This only applies to the cleaner, not the reporter. ↪ |
| --force-renderer-accessibility ⊗ | Force renderer accessibility to be on instead of enabling it on demand when a screen reader is detected. The disable-renderer-accessibility switch overrides this if present. ↪ |
| --force-self-delete ⊗ | Force self-deletion even on non-official builds. ↪ |
| --force-show-update-menu-badge[7] ⊗ | Forces the update menu badge to show. ↪ |
| --force-stacked-tab-strip-layout ⊗ | Forces Chrome to use a stacked tab strip layout. ↪ |
| --force-status-area-collapsible ⊗ | Forces the status area to allow collapse/expand regardless of the current state. ↪ |
| --force-system-compositor-mode ⊗ | Force system compositor mode when set. ↪ |
| --force-tablet-mode ⊗ | Enables required things for the selected UI mode, regardless of whether the Chromebook is currently in the selected UI mode. ↪ |
| --force-tablet-power-button ⊗ | If set, tablet-like power button behavior (i.e. tapping the button turns the screen off) is used even if the device is in laptop mode. ↪ |
| --force-text-direction ⊗ | Force the text rendering to a specific direction. Valid values are "ltr" (left-to-right) and "rtl" (right-to-left). Only tested meaningfully with RTL. ↪ |
| --force-ui-direction ⊗ | Force the UI to a specific direction. Valid values are "ltr" (left-to-right) and "rtl" (right-to-left). ↪ |
| --force-update-menu-type[7] ⊗ | Forces the update menu type to a specific type. ↪ |
| --force-update-remote-url ⊗ | Per-product customization of force update UI remote url, also used in testing. ↪ |
| --force-variation-ids ⊗ | Forces additional Chrome Variation Ids that will be sent in X-Client-Data header, specified as a 64-bit encoded list of numeric experiment ids. Ids prefixed with the character "t" will be treated as Trigger Variation Ids. ↪ |
| --force-video-overlays ⊗ | Force media player using SurfaceView instead of SurfaceTexture on Android. ↪ |
| --force-wave-audio[1] ⊗ | Use Windows WaveOut/In audio API even if Core Audio is supported. ↪ |
| --force-webrtc-ip-handling-policy ⊗ | Override WebRTC IP handling policy to mimic the behavior when WebRTC IP handling policy is specified in Preferences. ↪ |
| --force-webxr-runtime ⊗ | Forcibly enable and select the specified runtime for webxr. Note that this provides an alternative means of enabling a runtime, and will also functionally disable all other runtimes. ↪ |
| --frame-throttle-fps ⊗ | Sets the throttle fps for compositor frame submission. ↪ |
| --full-memory-crash-report ⊗ | Generates full memory crash dump. ↪ |
| --gaia-config ⊗ | No description ↪ |
| --gaia-url ⊗ | No description ↪ |
| --gamepad-polling-interval ⊗ | Overrides the gamepad polling interval. Decreasing the interval improves input latency of buttons and axes but may negatively affect performance due to more CPU time spent in the input polling thread. ↪ |
| --gcm-checkin-url ⊗ | Sets the checkin service endpoint that will be used for performing Google Cloud Messaging checkins. ↪ |
| --gcm-mcs-endpoint ⊗ | Sets the Mobile Connection Server endpoint that will be used for Google Cloud Messaging. ↪ |
| --gcm-registration-url ⊗ | Sets the registration endpoint that will be used for creating new Google Cloud Messaging registrations. ↪ |
| --generate-accessibility-test-expectations ⊗ | For development / testing only. When running content_browsertests, saves output of failing accessibility tests to their expectations files in content/test/data/accessibility/, overwriting existing file content. ↪ |
| --gl ⊗ | No description ↪ |
| --gl-egl ⊗ | No description ↪ |
| --gl-null ⊗ | No description ↪ |
| --gl-shader-interm-output ⊗ | Include ANGLE's intermediate representation (AST) output in shader compilation info logs. ↪ |
| --gles ⊗ | No description ↪ |
| --gles-egl ⊗ | No description ↪ |
| --gles-null ⊗ | No description ↪ |
| --google-apis-url ⊗ | No description ↪ |
| --google-base-url ⊗ | Specifies an alternate URL to use for speaking to Google. Useful for testing. ↪ |
| --google-doodle-url ⊗ | Overrides the URL used to fetch the current Google Doodle. Example: https://www.google.com/async/ddljson Testing? Try: https://www.gstatic.com/chrome/ntp/doodle_test/ddljson_android0.json https://www.gstatic.com/chrome/ntp/doodle_test/ddljson_android1.json https://www.gstatic.com/chrome/ntp/doodle_test/ddljson_android2.json https://www.gstatic.com/chrome/ntp/doodle_test/ddljson_android3.json https://www.gstatic.com/chrome/ntp/doodle_test/ddljson_android4.json ↪ |
| --google-url ⊗ | No description ↪ |
| --gpu ⊗ | No description ↪ |
| --gpu-blocklist-test-group ⊗ | Select a different set of GPU blocklist entries with the specified test_group ID. ↪ |
| --gpu-device-id ⊗ | Passes the active graphics device id from browser process to info collection GPU process. ↪ |
| --gpu-driver-bug-list-test-group ⊗ | Enable an extra set of GPU driver bug list entries with the specified test_group ID. Note the default test group (group 0) is still active. ↪ |
| --gpu-driver-version ⊗ | Passes the active graphics driver version from browser process to info collection GPU process. ↪ |
| --gpu-launcher ⊗ | Extra command line options for launching the GPU process (normally used for debugging). Use like renderer-cmd-prefix. ↪ |
| --gpu-no-context-lost ⊗ | Inform Chrome that a GPU context will not be lost in power saving mode, screen saving mode, etc. Note that this flag does not ensure that a GPU context will never be lost in any situations, say, a GPU reset. ↪ |
| --gpu-preferences ⊗ | Passes encoded GpuPreferences to GPU process. ↪ |
| --gpu-process ⊗ | Flags spied upon from other layers. ↪ |
| --gpu-program-cache-size-kb ⊗ | Sets the maximum size of the in-memory gpu program cache, in kb ↪ |
| --gpu-rasterization-msaa-sample-count ⊗ | The number of multisample antialiasing samples for GPU rasterization. Requires MSAA support on GPU to have an effect. 0 disables MSAA. ↪ |
| --gpu-revision ⊗ | Passes the active graphics revision info from browser process to info collection GPU process. ↪ |
| --gpu-sandbox-allow-sysv-shm ⊗ | Allows shmat() system call in the GPU sandbox. ↪ |
| --gpu-sandbox-failures-fatal ⊗ | Makes GPU sandbox failures fatal. ↪ |
| --gpu-sandbox-start-early ⊗ | Starts the GPU sandbox before creating a GL context. ↪ |
| --gpu-startup-dialog ⊗ | Causes the GPU process to display a dialog on launch. ↪ |
| --gpu-sub-system-id ⊗ | Passes the active graphics sub system id from browser process to info collection GPU process. ↪ |
| --gpu-vendor-id ⊗ | Passes the active graphics vendor id from browser process to info collection GPU process. ↪ |
| --gpu2-startup-dialog[1] ⊗ | Causes the second GPU process used for gpu info collection to display a dialog on launch. ↪ |
| --graphics-buffer-count ⊗ | No description ↪ |
| --guest[15] ⊗ | Causes the browser to launch directly in guest mode. ↪ |
| --guest-wallpaper-large ⊗ | Large wallpaper to use in guest mode (as path to trusted, non-user-writable JPEG file). ↪ |
| --guest-wallpaper-small ⊗ | Small wallpaper to use in guest mode (as path to trusted, non-user-writable JPEG file). ↪ |
| --h[9] ⊗ | No description ↪ |
| --has-chromeos-keyboard ⊗ | If set, the system is a Chromebook with a "standard Chrome OS keyboard", which generally means one with a Search key in the standard Caps Lock location above the Left Shift key. It should be unset for Chromebooks with both Search and Caps Lock keys (e.g. stout) and for devices like Chromeboxes that only use external keyboards. ↪ |
| --has-internal-stylus ⊗ | Whether this device has an internal stylus. ↪ |
| --headless ⊗ | Run in headless mode, i.e., without a UI or display server dependencies. ↪ |
| --help ⊗ | No description ↪ |
| --hermes-fake ⊗ | Enables Hermes fake behavior. By default, no carrier profiles are setup. If a value of "on" is passed for this switch, then hermes fakes are initialized with a single installed carrier profile. Fake cellular service corresponding to carrier profiles are also setup in Shill. ↪ |
| --hide ⊗ | "Hide" value for kCrosRegionsMode (VPD values are hidden). ↪ |
| --hide-android-files-in-files-app ⊗ | If true, files in Android internal storage will be hidden in Files app. ↪ |
| --hide-icons[1] ⊗ | Makes Windows happy by allowing it to show "Enable access to this program" checkbox in Add/Remove Programs->Set Program Access and Defaults. This only shows an error box because the only way to hide Chrome is by uninstalling it. ↪ |
| --hide-scrollbars ⊗ | Hide scrollbars from screenshots. ↪ |
| --highlight-all-webviews ⊗ | Highlight the contents (including web contents) of all WebViews with a yellow tint. This is useful for identifying WebViews in an Android application. ↪ |
| --highlight-non-lcd-text-layers ⊗ | Highlights layers that can't use lcd text. Layers containing no text won't be highlighted. See DebugColors::NonLCDTextHighlightColor() for the colors. ↪ |
| --homedir ⊗ | Defines user homedir. This defaults to primary user homedir. ↪ |
| --homepage ⊗ | Specifies which page will be displayed in newly-opened tabs. We need this for testing purposes so that the UI tests don't depend on what comes up for http://google.com. ↪ |
| --host ⊗ | No description ↪ |
| --host-resolver-rules ⊗ | These mappings only apply to the host resolver. ↪ |
| --https://chromemediarecommendations-pa.googleapis.com ⊗ | No description ↪ |
| --icon_reader[1] ⊗ | No description ↪ |
| --ignore-autocomplete-off-autofill ⊗ | Ignores autocomplete="off" for Autofill data (profiles + credit cards). ↪ |
| --ignore-certificate-errors-spki-list ⊗ | A set of public key hashes for which to ignore certificate-related errors. If the certificate chain presented by the server does not validate, and one or more certificates have public key hashes that match a key from this list, the error is ignored. The switch value must a be a comma-separated list of Base64-encoded SHA-256 SPKI Fingerprints (RFC 7469, Section 2.4). This switch has no effect unless --user-data-dir (as defined by the content embedder) is also present. ↪ |
| --ignore-google-port-numbers ⊗ | When set, this will ignore the PortPermission passed in the google_util.h methods and ignore the port numbers. This makes it easier to run tests for features that use these methods (directly or indirectly) with the EmbeddedTestServer, which is more representative of production. ↪ |
| --ignore-gpu-blacklist ⊗ | Ignores GPU blocklist. TODO(crbug.com/1101491): remove in 2020Q4 in favor of --ignore-gpu-blocklist. ↪ |
| --ignore-gpu-blocklist ⊗ | Ignores GPU blocklist. ↪ |
| --ignore-previews-blacklist ⊗ | Ignore decisions made by PreviewsBlockList. TODO(crbug.com/1092105) : Migrate this to ignore-previews-blacklist. ↪ |
| --ignore-urlfetcher-cert-requests ⊗ | Causes net::URLFetchers to ignore requests for SSL client certificates, causing them to attempt an unauthenticated SSL/TLS session. This is intended for use when testing various service URLs (eg: kPromoServerURL, kSbURLPrefix, kSyncServiceURL, etc). ↪ |
| --ignore-user-profile-mapping-for-tests ⊗ | If true, profile selection in UserManager will always return active user's profile. TODO(nkostlyev): http://crbug.com/364604 - Get rid of this switch after we turn on multi-profile feature on ChromeOS. ↪ |
| --ime[5] ⊗ | No description ↪ |
| --in-process-gpu ⊗ | Run the GPU process as a thread in the browser process. ↪ |
| --incognito ⊗ | No description ↪ |
| --init-done-notifier ⊗ | The handle of an event to signal when the initialization of the main process is complete (including loading all DLL's). This is used by the integration test to check that forbidden modules aren't loaded outside the sandbox. If this is set, the main process will signal the event and then wait for the integration test to signal it as well before continuing. Ignored in official builds. ↪ |
| --initial-virtual-time ⊗ | Start the renderer with an initial virtual time override specified in seconds since the epoch. ↪ |
| --input ⊗ | No description ↪ |
| --install-autogenerated-theme ⊗ | Installs an autogenerated theme based on the given RGB value. The format is "r,g,b", where r, g, b are a numeric values from 0 to 255. ↪ |
| --install-chrome-app ⊗ | Causes Chrome to initiate an installation flow for the given app. ↪ |
| --install-managed-bookmarks-handler ⊗ | Installs the managed bookmarks policy handler. ↪ |
| --install-supervised-user-whitelists ⊗ | A list of whitelists to install for a supervised user, for testing. The list is of the following form: |
| --install-url-blocklist-handlers ⊗ | Installs the URLBlocklist and URLAllowlist handlers. ↪ |
| --instant-process ⊗ | Marks a renderer as an Instant process. ↪ |
| --integration-test-timeout-minutes ⊗ | Set the timeout for integration tests in minutes. 0 disables the timeout entirely. ↪ |
| --ipc-connection-timeout ⊗ | Overrides the timeout, in seconds, that a child process waits for a connection from the browser before killing itself. ↪ |
| --ipc-dump-directory[18] ⊗ | Dumps IPC messages sent from renderer processes to the browser process to the given directory. Used primarily to gather samples for IPC fuzzing. ↪ |
| --ipc-fuzzer-testcase[18] ⊗ | Specifies the testcase used by the IPC fuzzer. ↪ |
| --isolate-origins ⊗ | Require dedicated processes for a set of origins, specified as a comma-separated list. For example: --isolate-origins=https://www.foo.com,https://www.bar.com ↪ |
| --javascript-harmony ⊗ | Enables experimental Harmony (ECMAScript 6) features. ↪ |
| --js-flags ⊗ | Specifies the flags passed to JS engine. ↪ |
| --kaleidoscope-backend-url ⊗ | A command line switch for overriding the base URL of the API. ↪ |
| --keep-alive-for-test ⊗ | Used for testing - keeps browser alive after last browser window closes. ↪ |
| --kernelnext-restrict-vms ⊗ | If set, the Chrome settings will not expose the option to enable crostini unless the enable-experimental-kernel-vm-support flag is set in chrome://flags ↪ |
| --kiosk ⊗ | Enable kiosk mode. Please note this is not Chrome OS kiosk mode. ↪ |
| --kiosk-printing ⊗ | Enable automatically pressing the print button in print preview. ↪ |
| --lacros-chrome-additional-args ⊗ | If this switch is set, then ash-chrome will pass additional arguments when launching lacros-chrome. The string '####' is used as a delimiter. Example: --lacros-chrome-additional-args="--foo=5####--bar=/tmp/dir name". Will result in two arguments passed to lacros-chrome: --foo=5 --bar=/tmp/dir name ↪ |
| --lacros-chrome-path ⊗ | If this switch is set, then ash-chrome will exec the lacros-chrome binary from the indicated path rather than from component updater. Note that the path should be to a directory that contains a binary named 'chrome'. ↪ |
| --lang ⊗ | The language file that we want to try to open. Of the form language[-country] where language is the 2 letter code from ISO-639. ↪ |
| --last-launched-app ⊗ | Pass the app id information to the renderer process, to be used for logging. last-launched-app should be the app that just launched and is spawning the renderer. ↪ |
| --layer ⊗ | No description ↪ |
| --light ⊗ | No description ↪ |
| --lite-video-default-downlink-bandwidth-kbps ⊗ | The default downlink bandwidth estimate used for throttling media requests. Only used when forcing LiteVideos to be allowed. ↪ |
| --lite-video-force-coinflip-holdback ⊗ | Forces the coinflip used for a counterfactual experiment to be true. ↪ |
| --lite-video-force-override-decision ⊗ | Overrides all the LiteVideo decision logic to allow it on every navigation. This causes LiteVideos to ignore the hints, user blocklist, and network condition. ↪ |
| --lite-video-ignore-network-conditions ⊗ | Overrides the network conditions checks for LiteVideos. ↪ |
| --load-and-launch-app ⊗ | Loads an app from the specified directory and launches it. ↪ |
| --load-apps ⊗ | Comma-separated list of paths to apps to load at startup. The first app in the list will be launched. ↪ |
| --load-empty-dll ⊗ | Attempt to load empty-dll.dll whenever this flag is set. For testing DLL loading. ↪ |
| --load-extension ⊗ | Comma-separated list of paths to extensions to load at startup. ↪ |
| --load-media-router-component-extension ⊗ | Loads the Media Router component extension on startup. ↪ |
| --load-signin-profile-test-extension[5] ⊗ | Path to the unpacked test extension to load into the signin profile. The ID extension loaded must match kTestSigninProfileExtensionId. ↪ |
| --local-sync-backend-dir ⊗ | Specifies the local sync backend directory. The name is chosen to mimic user-data-dir etc. This flag only matters if the enable-local-sync-backend flag is present. ↪ |
| --log-best-effort-tasks ⊗ | Logs information about all tasks posted with TaskPriority::BEST_EFFORT. Use this to diagnose issues that are thought to be caused by TaskPriority::BEST_EFFORT execution fences. Note: Tasks posted to a non-BEST_EFFORT UpdateableSequencedTaskRunner whose priority is later lowered to BEST_EFFORT are not logged. ↪ |
| --log-file ⊗ | Overrides the default file name to use for general-purpose logging (does not affect which events are logged). ↪ |
| --log-gpu-control-list-decisions ⊗ | Logs GPU control list decisions when enforcing blacklist rules. ↪ |
| --log-interface-calls-to ⊗ | Specifies a file to log all the interface calls of EngineRequestsImpl and CleanerEngineRequestsImpl. ↪ |
| --log-level ⊗ | Sets the minimum log level. Valid values are from 0 to 3: INFO = 0, WARNING = 1, LOG_ERROR = 2, LOG_FATAL = 3. ↪ |
| --log-net-log ⊗ | Enables saving net log events to a file. If a value is given, it used as the path the the file, otherwise the file is named netlog.json and placed in the user data directory. ↪ |
| --log-on-ui-double-background-blur[19] ⊗ | Checks and logs double background blur as an error if any. ↪ |
| --log-with-hash ⊗ | Log user actions with action name hashed. ↪ |
| --log-without-hash ⊗ | Log user actions with action name unhashed. ↪ |
| --login-manager ⊗ | Enables Chrome-as-a-login-manager behavior. ↪ |
| --login-profile ⊗ | Specifies the profile to use once a chromeos user is logged in. This parameter is ignored if user goes through login screen since user_id hash defines which profile directory to use. In case of browser restart within active session this parameter is used to pass user_id hash for primary user. ↪ |
| --login-user ⊗ | Specifies the user which is already logged in. ↪ |
| --logs-upload-retry-interval ⊗ | Specify the time to wait between logs upload retries, in minutes. ↪ |
| --lso-url ⊗ | No description ↪ |
| --ltr ⊗ | No description ↪ |
| --main-frame-resizes-are-orientation-changes ⊗ | Resizes of the main frame are caused by changing between landscape and portrait mode (i.e. Android) so the page should be rescaled to fit. ↪ |
| --make-chrome-default[6] ⊗ | Indicates whether Chrome should be set as the default browser during installation. ↪ |
| --make-default-browser ⊗ | Makes Chrome default browser ↪ |
| --managed-user-id ⊗ | Sets the supervised user ID for any loaded or newly created profile to the given value. Pass an empty string to mark the profile as non-supervised. Used for testing. ↪ |
| --mangle-localized-strings ⊗ | Transform localized strings to be longer, with beginning and end markers to make truncation visually apparent. ↪ |
| --manual ⊗ | No description ↪ |
| --market-url-for-testing[7] ⊗ | Sets the market URL for Chrome for use in testing. ↪ |
| --marketing-opt-in-url ⊗ | Determines the URL to be used when calling the backend. ↪ |
| --max-active-webgl-contexts ⊗ | Allows user to override maximum number of active WebGL contexts per renderer process. ↪ |
| --max-decoded-image-size-mb ⊗ | Sets the maximium decoded image size limitation. ↪ |
| --max-file-size ⊗ | Limit the size of files the scanning engine is allowed to open. ↪ |
| --max-gum-fps ⊗ | Override the maximum framerate as can be specified in calls to getUserMedia. This flag expects a value. Example: --max-gum-fps=17.5 ↪ |
| --max-output-volume-dba1m ⊗ | Calibrated max output volume dBa for voice content at 1 meter, if known. ↪ |
| --max-untiled-layer-height ⊗ | Sets the width and height above which a composited layer will get tiled. ↪ |
| --max-untiled-layer-width ⊗ | No description ↪ |
| --mem-pressure-system-reserved-kb ⊗ | Some platforms typically have very little 'free' memory, but plenty is available in buffers+cached. For such platforms, configure this amount as the portion of buffers+cached memory that should be treated as unavailable. If this switch is not used, a simple pressure heuristic based purely on free memory will be used. ↪ |
| --memlog ⊗ | No description ↪ |
| --memlog-sampling-rate ⊗ | No description ↪ |
| --memlog-stack-mode ⊗ | No description ↪ |
| --memory-pressure-off ⊗ | No description ↪ |
| --message-loop-type-ui ⊗ | Indicates the utility process should run with a message loop type of UI. ↪ |
| --metrics-client-id[6] ⊗ | This is how the metrics client ID is passed from the browser process to its children. With Crashpad, the metrics client ID is distinct from the crash client ID. ↪ |
| --metrics-recording-only ⊗ | Enables the recording of metrics reports but disables reporting. In contrast to kForceEnableMetricsReporting, this executes all the code that a normal client would use for reporting, except the report is dropped rather than sent to the server. This is useful for finding issues in the metrics code during UI and performance tests. ↪ |
| --metrics-upload-interval ⊗ | Override the standard time interval between each metrics report upload for UMA and UKM. It is useful to set to a short interval for debugging. Unit in seconds. (The default is 1800 seconds on desktop). ↪ |
| --min-height-for-gpu-raster-tile ⊗ | Sets the min tile height for GPU raster. ↪ |
| --minimal ⊗ | No description ↪ |
| --mixed ⊗ | No description ↪ |
| --mixer-enable-dynamic-channel-count ⊗ | Enable dynamically changing the channel count in the mixer depending on the input streams. ↪ |
| --mixer-service-endpoint ⊗ | Endpoint that the mixer service listens on. This is a path for a UNIX domain socket (default is /tmp/mixer-service). ↪ |
| --mixer-service-port ⊗ | TCP port that the mixer service listens on on non-Linux platforms. (default 12854). ↪ |
| --mixer-source-audio-ready-threshold-ms ⊗ | Specify the start threshold frames for audio output when using our mixer. This is mostly used to override the default value to a larger value, for platforms that can't handle the default start threshold without running into audio underruns. ↪ |
| --mixer-source-input-queue-ms ⊗ | Specify the buffer size for audio output when using our mixer. This is mostly used to override the default value to a larger value, for platforms that can't handle an audio buffer so small without running into audio underruns. ↪ |
| --mock ⊗ | No description ↪ |
| --mock-cert-verifier-default-result-for-testing ⊗ | Set the default result for MockCertVerifier. This only works in test code. ↪ |
| --mojo-core-library-path ⊗ | Initializes Mojo Core from a shared library at the specified path, rather than using the version of Mojo Core embedded within the Content executable. ↪ |
| --mojo-local-storage ⊗ | Use a Mojo-based LocalStorage implementation. ↪ |
| --mojo-pipe-token ⊗ | No description ↪ |
| --monitoring-destination-id ⊗ | Allows setting a different destination ID for connection-monitoring GCM messages. Useful when running against a non-prod management server. ↪ |
| --mse-audio-buffer-size-limit-mb ⊗ | Allows explicitly specifying MSE audio/video buffer sizes as megabytes. Default values are 150M for video and 12M for audio. ↪ |
| --mse-video-buffer-size-limit-mb ⊗ | No description ↪ |
| --mute-audio ⊗ | Mutes audio sent to the audio device so it is not audible during automated testing. ↪ |
| --nacl-broker ⊗ | No description ↪ |
| --nacl-dangerous-no-sandbox-nonsfi ⊗ | Disable sandbox even for non SFI mode. This is particularly unsafe as non SFI NaCl heavily relies on the seccomp sandbox. ↪ |
| --nacl-debug-mask ⊗ | Uses NaCl manifest URL to choose whether NaCl program will be debugged by debug stub. Switch value format: [!]pattern1,pattern2,...,patternN. Each pattern uses the same syntax as patterns in Chrome extension manifest. The only difference is that * scheme matches all schemes instead of matching only http and https. If the value doesn't start with !, a program will be debugged if manifest URL matches any pattern. If the value starts with !, a program will be debugged if manifest URL does not match any pattern. ↪ |
| --nacl-gdb ⊗ | Native Client GDB debugger that will be launched automatically when needed. ↪ |
| --nacl-gdb-script ⊗ | GDB script to pass to the nacl-gdb debugger at startup. ↪ |
| --nacl-loader ⊗ | No description ↪ |
| --nacl-loader-nonsfi ⊗ | Value for --type that causes the process to run as a NativeClient loader for non SFI mode. ↪ |
| --native ⊗ | No description ↪ |
| --native-messaging-connect-extension ⊗ | Requests a native messaging connection be established between the extension with ID specified by this switch and the native messaging host named by the kNativeMessagingConnectHost switch. ↪ |
| --native-messaging-connect-host ⊗ | Requests a native messaging connection be established between the native messaging host named by this switch and the extension with ID specified by kNativeMessagingConnectExtension. ↪ |
| --native-messaging-connect-id ⊗ | If set when kNativeMessagingConnectHost and kNativeMessagingConnectExtension are specified, is reflected to the native messaging host as a command line parameter. ↪ |
| --native-with-thread-names ⊗ | No description ↪ |
| --nearbysharing-http-host ⊗ | Overrides the default URL for Google APIs (https://www.googleapis.com) used by Nearby Share ↪ |
| --need-arc-migration-policy-check ⊗ | If present, the device needs to check the policy to see if the migration to ext4 for ARC is allowed. It should be present only on devices that have been initially issued with ecrypfs encryption and have ARC (N+) available. For the devices in other categories this flag must be missing. ↪ |
| --net-log-capture-mode ⊗ | Sets the granularity of events to capture in the network log. The mode can be set to one of the following values: "Default" "IncludeSensitive" "Everything" See the enums of the corresponding name in net_log_capture_mode.h for a description of their meanings. ↪ |
| --netifs-to-ignore ⊗ | List of network interfaces to ignore. Ignored interfaces will not be used for network connectivity. ↪ |
| --network ⊗ | No description ↪ |
| --network-country-iso[7] ⊗ | The telephony region (ISO country code) to use in phone number detection. ↪ |
| --network-quiet-timeout ⊗ | Sets the timeout seconds of the network-quiet timers in IdlenessDetector. Used by embedders who want to change the timeout time in order to run web contents on various embedded devices and changeable network bandwidths in different regions. For example, it's useful when using FirstMeaningfulPaint signal to dismiss a splash screen. ↪ |
| --new-canvas-2d-api ⊗ | Enable in-progress canvas 2d API features. ↪ |
| --new-window ⊗ | Launches URL in new browser window. ↪ |
| --no-crash-upload ⊗ | Prevent the crash client from uploading crash reports. ↪ |
| --no-default-browser-check ⊗ | Disables the default browser check. Useful for UI/browser tests where we want to avoid having the default browser info-bar displayed. ↪ |
| --no-delay-for-dx12-vulkan-info-collection ⊗ | Start the non-sandboxed GPU process for DX12 and Vulkan info collection immediately after the browser starts. The default is to delay for 120 seconds. ↪ |
| --no-experiments ⊗ | Disables all experiments set on about:flags. Does not disable about:flags itself. Useful if an experiment makes chrome crash at startup: One can start chrome with --no-experiments, disable the problematic lab at about:flags and then restart chrome without this switch again. ↪ |
| --no-first-run ⊗ | Skip First Run tasks, whether or not it's actually the First Run. Overridden by kForceFirstRun. This does not drop the First Run sentinel and thus doesn't prevent first run from occuring the next time chrome is launched without this flag. ↪ |
| --no-initial-navigation ⊗ | Stops new Shell objects from navigating to a default url. ↪ |
| --no-managed-user-acknowledgment-check ⊗ | Disables checking whether we received an acknowledgment when registering a supervised user. Also disables the timeout during registration that waits for the ack. Useful when debugging against a server that does not support notifications. ↪ |
| --no-network-profile-warning[1] ⊗ | Whether or not the browser should warn if the profile is on a network share. This flag is only relevant for Windows currently. ↪ |
| --no-pings ⊗ | Don't send hyperlink auditing pings ↪ |
| --no-proxy-server ⊗ | Don't use a proxy server, always make direct connections. Overrides any other proxy server flags that are passed. ↪ |
| --no-recovery-component ⊗ | Prevent downloading and running the recovery component. ↪ |
| --no-report-upload ⊗ | Prevent the logging service from uploading logs and reports. WARNING: this switch is used by internal test systems. Be careful when making changes. ↪ |
| --no-sandbox ⊗ | Disables the sandbox for all process types that are normally sandboxed. Meant to be used as a browser-level switch for testing purposes only. ↪ |
| --no-sandbox-and-elevated[1] ⊗ | Disables the sandbox and gives the process elevated privileges. ↪ |
| --no-self-delete ⊗ | Prevent the executable from deleting itself after running. ↪ |
| --no-service-autorun ⊗ | Disables the service process from adding itself as an autorun process. This does not delete existing autorun registrations, it just prevents the service from registering a new one. ↪ |
| --no-startup-window ⊗ | Does not automatically open a browser window on startup (used when launching Chrome for the purpose of hosting background apps). ↪ |
| --no-user-gesture-required ⊗ | Autoplay policy that does not require any user gesture. ↪ |
| --no-v8-untrusted-code-mitigations ⊗ | Disables V8 mitigations for executing untrusted code. ↪ |
| --no-vr-runtime ⊗ | Tell WebXr to assume that it does not support any runtimes. ↪ |
| --no-wifi ⊗ | Disable features that require WiFi management. ↪ |
| --no-xshm ⊗ | Disables MIT-SHM extension. ↪ |
| --no-zygote ⊗ | Disables the use of a zygote process for forking child processes. Instead, child processes will be forked and exec'd directly. Note that --no-sandbox should also be used together with this flag because the sandbox needs the zygote to work. ↪ |
| --no-zygote-sandbox[10] ⊗ | Instructs the zygote to launch without a sandbox. Processes forked from this type of zygote will apply their own custom sandboxes later. ↪ |
| --noerrdialogs ⊗ | Suppresses all error dialogs when present. ↪ |
| --none ⊗ | Must be in sync with "sandbox_type" values as used in service manager's manifest.json catalog files. ↪ |
| --none_and_elevated ⊗ | No description ↪ |
| --note-taking-app-ids ⊗ | An optional comma-separated list of IDs of apps that can be used to take notes. If unset, a hardcoded list is used instead. ↪ |
| --notification-inline-reply[1] ⊗ | Used in combination with kNotificationLaunchId to specify the inline reply entered in the toast in the Windows Action Center. ↪ |
| --notification-launch-id[1] ⊗ | Used for launching Chrome when a toast displayed in the Windows Action Center has been activated. Should contain the launch ID encoded by Chrome. ↪ |
| --ntp-snippets-add-incomplete ⊗ | If this flag is set, we will add downloaded snippets that are missing some critical data to the list. ↪ |
| --null ⊗ | No description ↪ |
| --num-raster-threads ⊗ | Number of worker threads used to rasterize content. ↪ |
| --oauth-account-manager-url ⊗ | No description ↪ |
| --oauth2-client-id ⊗ | No description ↪ |
| --oauth2-client-secret ⊗ | No description ↪ |
| --oculus ⊗ | The following are the runtimes that WebXr supports. ↪ |
| --offer-in-settings ⊗ | No description ↪ |
| --on-the-fly-mhtml-hash-computation ⊗ | Calculate the hash of an MHTML file as it is being saved. The browser process will write the serialized MHTML contents to a file and calculate its hash as it is streamed back from the renderer via a Mojo data pipe. ↪ |
| --oobe-eula-url-for-tests ⊗ | Allows the eula url to be overridden for tests. ↪ |
| --oobe-force-show-screen ⊗ | Forces OOBE/login to force show a comma-separated list of screens from chromeos::kScreenNames in oobe_screen.cc. Supported screens are: user-image ↪ |
| --oobe-force-tablet-first-run ⊗ | Indicates that the first user run flow (sequence of OOBE screens after the first user login) should show tablet mode centric screens, even if the device is not in tablet mode. ↪ |
| --oobe-guest-session ⊗ | Indicates that a guest session has been started before OOBE completion. ↪ |
| --oobe-screenshot-dir ⊗ | Specifies directory for screenshots taken with OOBE UI Debugger. ↪ |
| --oobe-skip-postlogin ⊗ | Skips all other OOBE pages after user login. ↪ |
| --oobe-skip-to-login ⊗ | Skip to login screen. ↪ |
| --oobe-timer-interval ⊗ | Interval at which we check for total time on OOBE. ↪ |
| --oobe-timezone-override-for-tests ⊗ | Allows the timezone to be overridden on the marketing opt-in screen. ↪ |
| --opengraph ⊗ | No description ↪ |
| --openvr ⊗ | No description ↪ |
| --openxr ⊗ | No description ↪ |
| --optimization-guide-fetch-hints-override ⊗ | Overrides scheduling and time delays for fetching hints and causes a hints fetch immediately on start up using the provided comma separate lists of hosts. ↪ |
| --optimization-guide-fetch-hints-override-timer ⊗ | Overrides the hints fetch scheduling and delay, causing a hints fetch immediately on start up using the TopHostProvider. This is meant for testing. ↪ |
| --optimization-guide-fetch-models-and-features-override ⊗ | Overrides scheduling and time delays for fetching prediction models and host model features. This causes a prediction model and host model features fetch immediately on start up. ↪ |
| --optimization-guide-service-api-key ⊗ | Overrides the Optimization Guide Service API Key for remote requests to be made. ↪ |
| --optimization-guide-service-get-hints-url ⊗ | Overrides the Optimization Guide Service URL that the HintsFetcher will request remote hints from. ↪ |
| --optimization-guide-service-get-models-url ⊗ | Overrides the Optimization Guide Service URL that the PredictionModelFetcher will request remote models and host features from. ↪ |
| --optimization_guide_hints_override ⊗ | Overrides the Hints Protobuf that would come from the component updater. If the value of this switch is invalid, regular hint processing is used. The value of this switch should be a base64 encoding of a binary Configuration message, found in optimization_guide's hints.proto. Providing a valid value to this switch causes Chrome startup to block on hints parsing. ↪ |
| --orientation-sensors ⊗ | No description ↪ |
| --origin-trial-disabled-features ⊗ | Contains a list of feature names for which origin trial experiments should be disabled. Names should be separated by "|" characters. ↪ |
| --origin-trial-disabled-tokens ⊗ | Contains a list of token signatures for which origin trial experiments should be disabled. Tokens should be separated by "|" characters. ↪ |
| --origin-trial-public-key ⊗ | Comma-separated list of keys which will override the default public keys for checking origin trial tokens. ↪ |
| --output ⊗ | No description ↪ |
| --override ⊗ | "Override" value for kCrosRegionsMode (region's data is read first). ↪ |
| --override-enabled-cdm-interface-version ⊗ | Overrides the default enabled library CDM interface version(s) with the one specified with this switch, which will be the only version enabled. For example, on a build where CDM 8, CDM 9 and CDM 10 are all supported (implemented), but only CDM 8 and CDM 9 are enabled by default: --override-enabled-cdm-interface-version=8 : Only CDM 8 is enabled --override-enabled-cdm-interface-version=9 : Only CDM 9 is enabled --override-enabled-cdm-interface-version=10 : Only CDM 10 is enabled --override-enabled-cdm-interface-version=11 : No CDM interface is enabled This can be used for local testing and debugging. It can also be used to enable an experimental CDM interface (which is always disabled by default) for testing while it's still in development. ↪ |
| --override-hardware-secure-codecs-for-testing ⊗ | Overrides hardware secure codecs support for testing. If specified, real platform hardware secure codecs check will be skipped. Codecs are separated by comma. Valid codecs are "vp8", "vp9" and "avc1". For example: --override-hardware-secure-codecs-for-testing=vp8,vp9 --override-hardware-secure-codecs-for-testing=avc1 CENC encryption scheme is assumed to be supported for the specified codecs. If no valid codecs specified, no hardware secure codecs are supported. This can be used to disable hardware secure codecs support: --override-hardware-secure-codecs-for-testing ↪ |
| --override-https-image-compression-infobar ⊗ | Override the one-time InfoBar to not needed to be shown before triggering https image compression for the page load. ↪ |
| --override-metrics-upload-url ⊗ | Override the URL to which metrics logs are sent for debugging. ↪ |
| --override-plugin-power-saver-for-testing ⊗ | Override the behavior of plugin throttling for testing. By default the throttler is only enabled for a hard-coded list of plugins. Set the value to 'always' to always throttle every plugin instance. Set the value to 'never' to disable throttling. ↪ |
| --override-use-software-gl-for-tests ⊗ | Forces the use of software GL instead of hardware gpu. ↪ |
| --ozone-dump-file ⊗ | Specify location for image dumps. ↪ |
| --ozone-platform ⊗ | Specify ozone platform implementation to use. ↪ |
| --pack-extension ⊗ | Packages an extension to a .crx installable file from a given directory. ↪ |
| --pack-extension-key ⊗ | Optional PEM private key to use in signing packaged .crx. ↪ |
| --parent-window ⊗ | No description ↪ |
| --passive-listeners-default ⊗ | Override the default value for the 'passive' field in javascript addEventListener calls. Values are defined as: 'documentonlytrue' to set the default be true only for document level nodes. 'true' to set the default to be true on all nodes (when not specified). 'forcealltrue' to force the value on all nodes. ↪ |
| --passthrough ⊗ | No description ↪ |
| --password-store ⊗ | Specifies which encryption storage backend to use. Possible values are kwallet, kwallet5, gnome, gnome-keyring, gnome-libsecret, basic. Any other value will lead to Chrome detecting the best backend automatically. TODO(crbug.com/571003): Once PasswordStore no longer uses the Keyring or KWallet for storing passwords, rename this flag to stop referencing passwords. Do not rename it sooner, though; developers and testers might rely on it keeping large amounts of testing passwords out of their Keyrings or KWallets. ↪ |
| --pdf_conversion[1] ⊗ | No description ↪ |
| --pen-devices[10] ⊗ | Tells chrome to interpret events from these devices as pen events. Only available with XInput 2 (i.e. X server 1.8 or above). The id's of the devices can be retrieved from 'xinput list'. ↪ |
| --perf-test-print-uma-means ⊗ | Show the mean value of histograms that native performance tests are monitoring. Note that this is only applicable for PerformanceTest subclasses. ↪ |
| --perfetto-disable-interning ⊗ | Repeat internable data for each TraceEvent in the perfetto proto format. ↪ |
| --perfetto-output-file ⊗ | If supplied, will enable Perfetto startup tracing and stream the output to the given file. On Android, if no file is provided, automatically generate a file to write the output to. TODO(oysteine): Remove once Perfetto starts early enough after process startup to be able to replace the legacy startup tracing. ↪ |
| --performance[5] ⊗ | No description ↪ |
| --permission-request-api-scope ⊗ | Development flag for permission request API. This flag is needed until the API is finalized. TODO(bauerb): Remove when this flag is not needed anymore. ↪ |
| --permission-request-api-url ⊗ | Development flag for permission request API. This flag is needed until the API is finalized. TODO(bauerb): Remove when this flag is not needed anymore. ↪ |
| --playready-key-system ⊗ | No description ↪ |
| --post-reboot ⊗ | Indicates this run is post-reboot. ↪ |
| --post-reboot-override-cmd ⊗ | Indicates that this is a post-reboot run that should fetch its switches from an external registry key. Important note: When this switch is present in the command line, all other switches are ignored except for kCleanupIdSwitch, which is used to read post-reboot switches from the correct registry location. ↪ |
| --post-reboot-trigger ⊗ | A freeform text string that records what triggered a post-reboot run. ↪ |
| --ppapi ⊗ | No description ↪ |
| --ppapi-antialiased-text-enabled[1] ⊗ | The boolean value (0/1) of FontRenderParams::antialiasing to be passed to Ppapi processes. ↪ |
| --ppapi-broker ⊗ | No description ↪ |
| --ppapi-flash-args ⊗ | "Command-line" arguments for the PPAPI Flash; used for debugging options. ↪ |
| --ppapi-flash-path ⊗ | Use the PPAPI (Pepper) Flash found at the given path. ↪ |
| --ppapi-flash-version ⊗ | Report the given version for the PPAPI (Pepper) Flash. The version should be numbers separated by '.'s (e.g., "12.3.456.78"). If not specified, it defaults to "10.2.999.999". ↪ |
| --ppapi-in-process ⊗ | Runs PPAPI (Pepper) plugins in-process. ↪ |
| --ppapi-plugin-launcher ⊗ | Specifies a command that should be used to launch the ppapi plugin process. Useful for running the plugin process through purify or quantify. Ex: --ppapi-plugin-launcher="path\to\purify /Run=yes" ↪ |
| --ppapi-startup-dialog ⊗ | Causes the PPAPI sub process to display a dialog on launch. Be sure to use --no-sandbox as well or the sandbox won't allow the dialog to display. ↪ |
| --ppapi-subpixel-rendering-setting[1] ⊗ | The enum value of FontRenderParams::subpixel_rendering to be passed to Ppapi processes. ↪ |
| --previous-app ⊗ | previous-app should be the app that was running when last-launched-app started. ↪ |
| --print-to-pdf ⊗ | Save a pdf file of the loaded page. ↪ |
| --print-to-pdf-no-header ⊗ | Do not display header and footer in the pdf file. ↪ |
| --print_compositor ⊗ | No description ↪ |
| --privet-ipv6-only ⊗ | Use IPv6 only for privet HTTP. ↪ |
| --process-per-site ⊗ | Enable the "Process Per Site" process model for all domains. This mode consolidates same-site pages so that they share a single process. More details here: - https://www.chromium.org/developers/design-documents/process-models - The class comment in site_instance.h, listing the supported process models. IMPORTANT: This isn't to be confused with --site-per-process (which is about isolation, not consolidation). You probably want the other one. ↪ |
| --process-per-tab ⊗ | Runs each set of script-connected tabs (i.e., a BrowsingInstance) in its own renderer process. We default to using a renderer process for each site instance (i.e., group of pages from the same registered domain with script connections to each other). TODO(creis): This flag is currently a no-op. We should refactor it to avoid "unnecessary" process swaps for cross-site navigations but still swap when needed for security (e.g., isolated origins). ↪ |
| --prod ⊗ | The command line alias and URL for the "prod" environment. ↪ |
| --product-version ⊗ | Outputs the product version information and quit. Used as an internal api to detect the installed version of Chrome on Linux. ↪ |
| --profile-directory ⊗ | Selects directory of profile to associate with the first browser launched. ↪ |
| --profile-requires-policy ⊗ | If set to "true", the profile requires policy during restart (policy load must succeed, otherwise session restart should fail). ↪ |
| --profiling-at-start ⊗ | Starts the sampling based profiler for the browser process at startup. This will only work if chrome has been built with the gn arg enable_profiling = true. The output will go to the value of kProfilingFile. ↪ |
| --profiling-file ⊗ | Specifies a location for profiling output. This will only work if chrome has been built with the gyp variable profiling=1 or gn arg enable_profiling=true. {pid} if present will be replaced by the pid of the process. {count} if present will be incremented each time a profile is generated for this process. The default is chrome-profile-{pid} for the browser and test-profile-{pid} for tests. ↪ |
| --profiling-flush ⊗ | Controls whether profile data is periodically flushed to a file. Normally the data gets written on exit but cases exist where chromium doesn't exit cleanly (especially when using single-process). A time in seconds can be specified. ↪ |
| --progress-bar-animation[7] ⊗ | Specifies Android phone page loading progress bar animation. ↪ |
| --proxy-auto-detect ⊗ | Forces proxy auto-detection. ↪ |
| --proxy-bypass-list ⊗ | Specifies a list of hosts for whom we bypass proxy settings and use direct connections. Ignored unless --proxy-server is also specified. This is a comma-separated list of bypass rules. See: "net/proxy_resolution/proxy_bypass_rules.h" for the format of these rules. ↪ |
| --proxy-pac-url ⊗ | Uses the pac script at the given URL ↪ |
| --proxy-server ⊗ | Uses a specified proxy server, overrides system settings. This switch only affects HTTP and HTTPS requests. ↪ |
| --proxy_resolver[1] ⊗ | No description ↪ |
| --pseudo ⊗ | No description ↪ |
| --public-accounts-saml-acl-url ⊗ | SAML assertion consumer URL, used to detect when Gaia-less SAML flows end (e.g. for SAML managed guest sessions) TODO(984021): Remove when URL is sent by DMServer. ↪ |
| --pull-to-refresh ⊗ | Enables or disables pull-to-refresh gesture in response to vertical overscroll. Set the value to '0' to disable the feature, set to '1' to enable it for both touchpad and touchscreen, and set to '2' to enable it only for touchscreen. Defaults to disabled. ↪ |
| --purge-model-and-features-store ⊗ | Purges the store containing prediction medels and host model features on startup, so that it's guaranteed to be using fresh data. ↪ |
| --purge-optimization-guide-store ⊗ | Purges the store containing fetched and component hints on startup, so that it's guaranteed to be using fresh data. ↪ |
| --pwa-launcher-version[1] ⊗ | Specifies the version of the Progressive-Web-App launcher that launched Chrome, used to determine whether to update all launchers. NOTE: changing this switch requires adding legacy handling for the previous method, as older PWA launchers still using this switch will rely on Chrome to update them to use the new method. ↪ |
| --quarantine-dir ⊗ | Specifies the quarantine folder instead of the default one. ↪ |
| --query-tiles-country-code ⊗ | No description ↪ |
| --query-tiles-instant-background-task ⊗ | No description ↪ |
| --query-tiles-single-tier ⊗ | No description ↪ |
| --rdp_desktop_session ⊗ | No description ↪ |
| --reached-code-sampling-interval-us[7] ⊗ | Specifies the profiling interval in microseconds for reached code profiler. ↪ |
| --reader-mode-feedback ⊗ | No description ↪ |
| --reader-mode-heuristics ⊗ | No description ↪ |
| --realtime-reporting-url ⊗ | Specifies the URL at which to upload real-time reports. ↪ |
| --redirect-libassistant-logging ⊗ | Redirects libassistant logging to /var/log/chrome/. ↪ |
| --register-font-files[1] ⊗ | Registers additional font files on Windows (for fonts outside the usual %WINDIR%\Fonts location). Multiple files can be used by separating them with a semicolon (;). ↪ |
| --register-max-dark-suspend-delay ⊗ | Makes Chrome register the maximum dark suspend delay possible on Chrome OS i.e. give the device the maximum amount of time to do its work in dark resume as is allowed by the power manager. ↪ |
| --register-pepper-plugins ⊗ | Register Pepper plugins (see pepper_plugin_list.cc for its format). ↪ |
| --regulatory-label-dir ⊗ | The name of the per-model directory which contains per-region subdirectories with regulatory label files for this model. The per-model directories (if there are any) are located under "/usr/share/chromeos-assets/regulatory_labels/". ↪ |
| --relauncher[6] ⊗ | A process type (switches::kProcessType) that relaunches the browser. See chrome/browser/mac/relauncher.h. ↪ |
| --remote-debugger-handles ⊗ | No description ↪ |
| --remote-debugging-address ⊗ | Use the given address instead of the default loopback for accepting remote debugging connections. Should be used together with --remote-debugging-port. Note that the remote debugging protocol does not perform any authentication, so exposing it too widely can be a security risk. ↪ |
| --remote-debugging-pipe ⊗ | Enables remote debug over stdio pipes [in=3, out=4]. Optionally, specifies the format for the protocol messages, can be either "JSON" (the default) or "CBOR". ↪ |
| --remote-debugging-port ⊗ | Enables remote debug over HTTP on the specified port. ↪ |
| --remote-debugging-socket-name[7] ⊗ | Enables remote debug over HTTP on the specified socket name. ↪ |
| --remote-debugging-targets ⊗ | Porvides a list of addresses to discover DevTools remote debugging targets. The format is |
| --remove-scan-only-uws ⊗ | Allow the engine to remove UwS that isn't marked cleanable. For testing only. ↪ |
| --renderer ⊗ | No description ↪ |
| --renderer-client-id ⊗ | No description ↪ |
| --renderer-cmd-prefix ⊗ | The contents of this flag are prepended to the renderer command line. Useful values might be "valgrind" or "xterm -e gdb --args". ↪ |
| --renderer-process-limit ⊗ | Overrides the default/calculated limit to the number of renderer processes. Very high values for this setting can lead to high memory/resource usage or instability. ↪ |
| --renderer-sampling ⊗ | No description ↪ |
| --renderer-startup-dialog ⊗ | Causes the renderer process to display a dialog on launch. Passing this flag also adds sandbox::policy::kNoSandbox on Windows non-official builds, since that's needed to show a dialog. ↪ |
| --renderer-wait-for-java-debugger[7] ⊗ | Block ChildProcessMain thread of the renderer's ChildProcessService until a Java debugger is attached. ↪ |
| --renderpass ⊗ | Parameters for kUIShowCompositedLayerBorders. ↪ |
| --repl ⊗ | Runs a read-eval-print loop that allows the user to evaluate Javascript expressions. ↪ |
| --report-vp9-as-an-unsupported-mime-type ⊗ | Force to report VP9 as an unsupported MIME type. ↪ |
| --require-audio-hardware-for-testing ⊗ | When running tests on a system without the required hardware or libraries, this flag will cause the tests to fail. Otherwise, they silently succeed. ↪ |
| --require-wlan ⊗ | Only connect to WLAN interfaces. ↪ |
| --reset-variation-state ⊗ | Forces a reset of the one-time-randomized FieldTrials on this client, also known as the Chrome Variations state. ↪ |
| --restore-last-session ⊗ | Indicates the last session should be restored on startup. This overrides the preferences value. Note that this does not force automatic session restore following a crash, so as to prevent a crash loop. This switch is used to implement support for OS-specific "continue where you left off" functionality on OS X and Windows. ↪ |
| --restrict-gamepad-access ⊗ | Enables Feature Policy and Secure Context requirements on getGamepads. ↪ |
| --rlz-ping-delay ⊗ | The rlz ping delay (in seconds) that overwrites the default value. ↪ |
| --rtl ⊗ | No description ↪ |
| --run-all-compositor-stages-before-draw ⊗ | Effectively disables pipelining of compositor frame production stages by waiting for each stage to finish before completing a frame. ↪ |
| --run-manual ⊗ | Manual tests only run when --run-manual is specified. This allows writing tests that don't run automatically but are still in the same test binary. This is useful so that a team that wants to run a few tests doesn't have to add a new binary that must be compiled on all builds. ↪ |
| --run-web-tests ⊗ | Runs Content Shell in web test mode, injecting test-only behaviour for blink web tests. ↪ |
| --run-without-sandbox-for-testing[3] ⊗ | Load the engine outside the sandbox. This is only to be used for manual testing. ↪ |
| --safe-mode ⊗ | The switch added by session_manager daemon when chrome crashes 3 times or more within the first 60 seconds on start. See BrowserJob::ExportArgv in platform2/login_manager/browser_job.cc. ↪ |
| --safebrowsing-enable-enhanced-protection ⊗ | Enable Safe Browsing Enhanced Protection. ↪ |
| --safebrowsing-manual-download-blacklist ⊗ | List of comma-separated sha256 hashes of executable files which the download-protection service should treat as "dangerous." For a file to show a warning, it also must be considered a dangerous filetype and not be whitelisted otherwise (by signature or URL) and must be on a supported OS. Hashes are in hex. This is used for manual testing when looking for ways to by-pass download protection. ↪ |
| --SafeSites ⊗ | No description ↪ |
| --saml-password-change-url ⊗ | Password change url for SAML users. TODO(941489): Remove when the bug is fixed. ↪ |
| --sandbox-ipc ⊗ | Causes the process to run as a sandbox IPC subprocess. ↪ |
| --sandbox-mojo-pipe-token ⊗ | Mojo pipe token generated in the broker process and passed to the sandbox process to bind with the EngineCommands IPC interface. ↪ |
| --sandboxed-process-id ⊗ | Used to identify the id of the sandbox process that is intended to be spawned. ↪ |
| --save-page-as-mhtml ⊗ | Disable saving pages as HTML-only, disable saving pages as HTML Complete (with a directory of sub-resources). Enable only saving pages as MHTML. See http://crbug.com/120416 for how to remove this switch. ↪ |
| --scan-locations ⊗ | Used to limit trace locations that will be scanned. Trace locations should be specified as integers, separated by commas. For example: --scan-locations=1,2,3,5 ↪ |
| --scanning-timeout ⊗ | Set the timeout for the scanning phase, in minutes. 0 disables the timeout entirely. WARNING: this switch is used by internal test systems. Be careful when making changes. ↪ |
| --scheduler-configuration[5] ⊗ | Selects the scheduler configuration specified in the parameter. ↪ |
| --scheduler-configuration-default[5] ⊗ | Specifies what the default scheduler configuration value is if the user does not set one. ↪ |
| --screen-config ⊗ | Specifies the initial screen configuration, or state of all displays, for FakeDisplayDelegate, see class for format details. ↪ |
| --screenshot ⊗ | Save a screenshot of the loaded page. ↪ |
| --search-provider-logo-url ⊗ | Use a static URL for the logo of the default search engine. Example: https://www.google.com/branding/logo.png ↪ |
| --secondary-display-layout ⊗ | Specifies the layout mode and offsets for the secondary display for testing. The format is " |
| --service ⊗ | No description ↪ |
| --service-manager ⊗ | The value of the |kProcessType| switch which tells the executable to assume the role of a standalone Service Manager instance. ↪ |
| --service-name ⊗ | Indicates the name of the service to run. Useful for debugging, or if a service executable is built to support being run as a number of potential different services. ↪ |
| --service-request-attachment-name ⊗ | The name of the |mojo::PendingReceiver |
| --service-request-channel-token ⊗ | The token to use to construct the message pipe for a service in a child process. ↪ |
| --service-runner ⊗ | The value of the |kProcessType| switch which tells the executable to assume the role of a service instance. ↪ |
| --service-sandbox-type ⊗ | Type of sandbox to apply to the process running the service, one of the values in the next block. ↪ |
| --set-extension-throttle-test-params ⊗ | Set the parameters for ExtensionURLLoaderThrottleBrowserTest. ↪ |
| --shader-disk-cache-size-kb ⊗ | Allows explicitly specifying the shader disk cache size for embedded devices. Default value is 6MB. On Android, 2MB is default and 128KB for low-end devices. ↪ |
| --shared-files ⊗ | Describes the file descriptors passed to a child process in the following list format: |
| --sharing_service ⊗ | No description ↪ |
| --shelf-hotseat ⊗ | New modular design for the shelf with apps separated into a hotseat UI and smaller shelf in clamshell mode. ↪ |
| --shelf-hover-previews ⊗ | App window previews when hovering over the shelf. ↪ |
| --shill-stub ⊗ | Overrides Shill stub behavior. By default, ethernet, wifi and are enabled, and transitions occur instantaneously. Multiple options can be comma separated (no spaces). Note: all options are in the format 'foo=x'. Values are case sensitive and based on Shill names in service_constants.h. See FakeShillManagerClient::SetInitialNetworkState for implementation. Examples: 'clear=1' - Clears all default configurations 'wifi=on' - A wifi network is initially connected ('1' also works) 'wifi=off' - Wifi networks are all initially disconnected ('0' also works) 'wifi=disabled' - Wifi is initially disabled 'wifi=none' - Wifi is unavailable 'wifi=portal' - Wifi connection will be in Portal state 'cellular=1' - Cellular is initially connected 'cellular=LTE' - Cellular is initially connected, technology is LTE 'interactive=3' - Interactive mode, connect/scan/etc requests take 3 secs ↪ |
| --short-merge-session-timeout-for-test[5] ⊗ | Use a short (1 second) timeout for merge session loader throttle testing. ↪ |
| --short-reporting-delay ⊗ | Sets the Reporting API delay to under a second to allow much quicker reports. ↪ |
| --show-aggregated-damage ⊗ | Adds a DebugBorderDrawQuad to the top of the root RenderPass showing the damage rect after surface aggregation. Note that when enabled this feature sets the entire output rect as damaged after adding the quad to highlight the real damage rect, which could hide damage rect problems. ↪ |
| --show-android-files-in-files-app ⊗ | If true, files in Android internal storage will be shown in Files app. ↪ |
| --show-auth-dialog-dev-overlay ⊗ | If true, the debug view overlay will be shown for the in-session authentication dialog. This enables development of the dialog. TODO(yichenli): Remove this after the feature is released. ↪ |
| --show-autofill-signatures ⊗ | Annotates forms and fields with Autofill signatures. ↪ |
| --show-autofill-type-predictions ⊗ | Annotates forms with Autofill field type predictions. ↪ |
| --show-component-extension-options ⊗ | Makes component extensions appear in chrome://settings/extensions. ↪ |
| --show-composited-layer-borders ⊗ | Renders a border around compositor layers to help debug and study layer compositing. ↪ |
| --show-dc-layer-debug-borders ⊗ | Show debug borders for DC layers - red for overlays and blue for underlays. The debug borders are offset from the layer rect by a few pixels for clarity. ↪ |
| --show-fps-counter ⊗ | Draws a heads-up-display showing Frames Per Second as well as GPU memory usage. If you also use --enable-logging=stderr --vmodule="head*=1" then FPS will also be output to the console log. ↪ |
| --show-icons[1] ⊗ | See kHideIcons. ↪ |
| --show-layer-animation-bounds ⊗ | Renders a border that represents the bounding box for the layer's animation. ↪ |
| --show-layout-shift-regions ⊗ | Visibly render a border around layout shift rects in the web page to help debug and study layout shifts. ↪ |
| --show-login-dev-overlay ⊗ | If true, the developer tool overlay will be shown for the login/lock screen. This makes it easier to test layout logic. ↪ |
| --show-mac-overlay-borders[6] ⊗ | Show borders around CALayers corresponding to overlays and partial damage. ↪ |
| --show-oobe-dev-overlay ⊗ | Enables OOBE UI Debugger for ease of navigation between screens during manual testing. Limited to ChromeOS-on-linux and test images only. ↪ |
| --show-overdraw-feedback ⊗ | Visualize overdraw by color-coding elements based on if they have other elements drawn underneath. This is good for showing where the UI might be doing more rendering work than necessary. The colors are hinting at the amount of overdraw on your screen for each pixel, as follows: True color: No overdraw. Blue: Overdrawn once. Green: Overdrawn twice. Pink: Overdrawn three times. Red: Overdrawn four or more times. ↪ |
| --show-paint-rects ⊗ | Visibly render a border around paint rects in the web page to help debug and study painting behavior. ↪ |
| --show-property-changed-rects ⊗ | Show rects in the HUD around layers whose properties have changed. ↪ |
| --show-screenspace-rects ⊗ | Show rects in the HUD around the screen-space transformed bounds of every layer. ↪ |
| --show-surface-damage-rects ⊗ | Show rects in the HUD around damage as it is recorded into each render surface. ↪ |
| --show-taps ⊗ | Draws a circle at each touch point, similar to the Android OS developer option "Show taps". ↪ |
| --silent-debugger-extension-api ⊗ | Does not show an infobar when an extension attaches to a page using chrome.debugger page. Required to attach to extension background pages. ↪ |
| --silent-launch ⊗ | Causes Chrome to launch without opening any windows by default. Useful if one wishes to use Chrome as an ash server. ↪ |
| --simulate-critical-update ⊗ | Simulates a critical update being available. ↪ |
| --simulate-elevated-recovery ⊗ | Simulates that elevation is needed to recover upgrade channel. ↪ |
| --simulate-outdated ⊗ | Simulates that current version is outdated. ↪ |
| --simulate-outdated-no-au ⊗ | Simulates that current version is outdated and auto-update is off. ↪ |
| --simulate-update-error-code ⊗ | Simulates a GoogleUpdateErrorCode error by the update check. Must be supplied with |kSimulateUpdateHresult| switch. ↪ |
| --simulate-update-hresult ⊗ | Simulates a specific HRESULT error code returned by the update check. If the switch value is not specified (as hex) then it defaults to E_FAIL. ↪ |
| --simulate-upgrade ⊗ | Simulates an update being available. ↪ |
| --single-process ⊗ | Runs the renderer and plugins in the same process as the browser ↪ |
| --site-per-process ⊗ | Enforces a one-site-per-process security policy: * Each renderer process, for its whole lifetime, is dedicated to rendering pages for just one site. * Thus, pages from different sites are never in the same process. * A renderer process's access rights are restricted based on its site. * All cross-site navigations force process swaps. * |