google-chrome(1)

πŸ“¦ version 149.0.7827.114, in ubuntu questing

πŸ’– google-chrome(1) β€” NAME πŸ’–

okay so google-chrome is the web browser from Google 🌈 literally the one you open every single day, bestie πŸ’…


✨ SYNOPSIS ✨

google-chrome [OPTION] [PATH|URL]

πŸŽ€ DESCRIPTION πŸŽ€

ngl the browser has its own help center for when you're stuck, so go check it out 🫢

<https://support.google.com/chrome/>

this manpage only covers invocation, environment, and arguments. that's it, that's the tea β˜•


🌸 OPTIONS 🌸

okay so Google Chrome has hundreds of undocumented command-line flags πŸ’€ they get added and removed whenever the developers feel like it. so here, we only document the relatively stable ones, no cap πŸ¦‹

  • --user-data-dir=DIR β€” this is where your "profile" (all your user data) lives πŸ’œ it defaults to $HOME/.config/google-chrome. separate Chrome instances need separate user data directories, and if you run google-chrome again it'll just reuse an existing process for that directory 🧚
  • --incognito β€” opens in incognito mode πŸ™ˆ
  • --new-window β€” if a PATH or URL is given, it opens in a brand new window ✨
  • --proxy-server=host:port β€” picks the HTTP/SOCKS4/SOCKS5 proxy for requests πŸ”₯ this overrides any environment variables or settings from the options dialog. each proxy is written like this:
[<proxy-scheme>://]<proxy-host>[:<proxy-port>]

where <proxy-scheme> is the protocol and is one of "http", "socks", "socks4", or "socks5". if you skip the scheme it defaults to "http", and "socks" is the same thing as "socks5" πŸŽ€

examples bestie, look at these:

--proxy-server="foopy:99"
    Use the HTTP proxy "foopy:99" to load all URLs.

--proxy-server="socks://foobar:1080"
    Use the SOCKS v5 proxy "foobar:1080" to load all URLs.

--proxy-server="socks4://foobar:1080"
    Use the SOCKS v4 proxy "foobar:1080" to load all URLs.

--proxy-server="socks5://foobar:66"
    Use the SOCKS v5 proxy "foobar:66" to load all URLs.

you can also give different URL types their own proxy by putting a URL specifier in front of the proxy spec 🧁

example:

--proxy-server="https=proxy1:80;http=socks4://baz:1080"
    Load https://* URLs using the HTTP proxy "proxy1:80". And
load http://*
    URLs using the SOCKS v4 proxy "baz:1080".
  • --no-proxy-server β€” disables the proxy server entirely πŸ™… overrides any environment variables or settings from the options dialog too
  • --proxy-auto-detect β€” autodetects the proxy configuration πŸ” also overrides env variables and dialog settings
  • --proxy-pac-url=URL β€” specifies a proxy autoconfiguration URL πŸ—ΊοΈ overrides env variables and dialog settings as well
  • --password-store=<basic|gnome|kwallet> β€” picks where passwords get stored πŸ” the default is to auto-detect based on your desktop environment. basic is the built-in unencrypted store, gnome is the Gnome keyring, and kwallet is (KDE) KWallet. ⚠️ heads up, KWallet might not work reliably outside KDE
  • --version β€” shows version info 🌈
Google Chrome is a GTK+ app, so it also obeys GTK+ command-line flags, like --display. for more deets check out: <http://library.gnome.org/devel/gtk/stable/gtk-running.html> <http://library.gnome.org/devel/gtk/stable/gtk-x11.html>

🧚 ENVIRONMENT 🧚

Google Chrome listens to these environment variables, periodt πŸ’…

  • all_proxy β€” shorthand for setting http_proxy, https_proxy, and ftp_proxy all at once 🫢
  • http_proxy, https_proxy, ftp_proxy β€” the proxy servers used for HTTP, HTTPS, and FTP 😭 ngl this one's tricky: because Gnome/KDE proxy settings can leak into these variables in some terminals, they get ignored (in favor of the actual system proxy settings) when running under Gnome or KDE. if you want to force their values, use the command-line flags instead πŸ™ˆ
  • auto_proxy β€” specifies proxy autoconfiguration. if it's defined and empty, it autodetects; otherwise it should be an autoconfig URL. but see the Gnome/KDE note above πŸ‘€
  • SOCKS_SERVER β€” the SOCKS proxy server (it defaults to SOCKS v4, but set SOCKS_VERSION=5 to use SOCKS v5) 🧦
  • no_proxy β€” a comma separated list of hosts or patterns to skip proxying for πŸ¦‹

πŸ“ FILES πŸ“

  • $HOME/.config/google-chrome β€” the default directory for configuration data βš™οΈ
  • $HOME/.cache/google-chrome β€” the default directory for cache data πŸ“ (wondering why it's here? see <http://standards.freedesktop.org/basedir-spec/latest/> πŸ€“)

πŸ› BUGS πŸ›

bugs happen, bestie πŸ₯Ί the bug tracker lives at:

http://code.google.com/p/chromium/issues/list

before you report anything, make sure you search within "All Issues" first, and pick the "Defect on Linux" template when filing a new one πŸ“


πŸ‘‘ AUTHOR πŸ‘‘

the Chromium team πŸ’œ <http://www.chromium.org>


that's the whole google-chrome(1) manual, bestie! 🌈 it's from google-chrome(1) USER COMMANDS, so you know it's legit 🫢 slay forever πŸ’…βœ¨

πŸ“¦ where this page comes from