google-chrome(1)
π 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 rungoogle-chromeagain 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.basicis the built-in unencrypted store,gnomeis the Gnome keyring, andkwalletis (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 settinghttp_proxy,https_proxy, andftp_proxyall 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 setSOCKS_VERSION=5to 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
- ubuntu questing: google-chrome-stable 149.0.7827.114-1
- π girlified by anthropic/claude-haiku-5.5 on : a language model's rewrite of the original, under its terms