chromium-browser(1)

💅 chromium-browser(1) — USER COMMANDS, bestie

okay so. this is the manpage for chromium-browser, and it lives in the USER COMMANDS corner of the manual (section 1, if you're keeping score 🎀). it's the whole vibe of how you launch the thing, not how you click around inside it.

---

✨ NAME ✨

chromium-browser — the web browser from Google. that's it, that's the name, iconic behavior honestly 👑

---

🌸 SYNOPSIS 🌸

chromium-browser [OPTION] [PATH|URL]

so like. you give it options, you give it a path or a URL, and it does its lil browser thing. simple as 💖

---

🦋 DESCRIPTION 🦋

for actual help using the browser, the page says go check the Google Chrome help center:

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

and this manpage? it only covers invocation, environment, and arguments. that's the whole scope, no cap. it is NOT gonna teach you how to close a tab, bestie, that's on you 🫶

---

✨ OPTIONS ✨

okay real talk: Chromium has hundreds of undocumented command-line flags that get added and removed at the whim of the developers 😭. so this page only documents the relatively stable ones. the rest are giving chaos, and we respect that, but we're not writing them down.

• --user-data-dir=DIR — tells Chromium where to keep your user data (aka your "profile"). default is $HOME/.config/chromium-browser. important: separate instances of Chromium must use separate user data directories, no sharing. and if you run chromium-browser again with the same user data directory, it just reuses the process that's already running. periodt.
• --incognito — opens in incognito mode. you know what this is. don't pretend you don't 🙈
• --new-window — if a PATH or URL is given, open it in a new window.
• --proxy-server=host:port — picks the HTTP/SOCKS4/SOCKS5 proxy server for requests. this overrides any environment variables or settings you picked through the options dialog. the format for an individual proxy server is:

[<proxy-scheme>://]<proxy-host>[:<proxy-port>]

where <proxy-scheme> is the protocol of the proxy server, and it's one of:

"http", "socks", "socks4", "socks5".

if <proxy-scheme> is omitted, it defaults to "http". also note that "socks" is equivalent to "socks5". (the way that's a whole gotcha, iykyk 💀)

examples, bestie:

--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.

and you can also set a separate proxy server for different URL types, by prefixing the proxy server specifier with a URL specifier. 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 picked via the options dialog. bye proxy 👋
• --proxy-auto-detect — autodetects proxy configuration. also overrides any environment variables or settings picked via the options dialog. she's independent like that ✨
• --proxy-pac-url=URL — specifies the proxy autoconfiguration URL. yep, you guessed it: overrides any environment variables or settings picked via the options dialog. 💅
• --password-store=<basic|gnome|kwallet> — sets which password store to use. the default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. heads up: KWallet may not work reliably outside KDE — that's not a vibe, that's a warning ⚠️
• --version — shows version information. the classic. the iconique. 👑

also, as a GTK+ app, Chromium obeys GTK+ command-line flags too, like --display. for more on that, see the GTK documentation:

<http://library.gnome.org/devel/gtk/stable/gtk-running.html>

<http://library.gnome.org/devel/gtk/stable/gtk-x11.html>

---

🌈 ENVIRONMENT 🌈

Chromium obeys these environment variables, bestie, write them down:

• all_proxy — shorthand for specifying all of http_proxy, https_proxy, ftp_proxy. one var to rule them all 🫶
• http_proxy, https_proxy, ftp_proxy — the proxy servers used for HTTP, HTTPS, and FTP. note: because Gnome/KDE proxy settings may propagate into these variables in some terminals, this variable is ignored (in preference for actual system proxy settings) when running under Gnome or KDE. so if you wanna force their values, use the command-line flags. no cap, that's the move.
• auto_proxy — specifies proxy autoconfiguration. defined and empty = autodetects; otherwise it should be an autoconfig URL. but see the note above about Gnome/KDE 👀
• SOCKS_SERVER — SOCKS proxy server. defaults to SOCKS v4, and you also set SOCKS_VERSION=5 to use SOCKS v5.
• no_proxy — comma separated list of hosts or patterns to bypass proxying. the "not you" list 🚫

---

🎀 FILES 🎀

• $HOME/.config/chromium-browser — default directory for configuration data.
• $HOME/.cache/chromium-browser — default directory for cache data. (why? see <http://standards.freedesktop.org/basedir-spec/latest/> .) yes the "why?" is literally in the original, we're all just living here 😭

---

💀 BUGS 💀

bug tracker:

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

and listen, before you file anything: be sure to do your search within "All Issues" before reporting bugs, and be sure to pick the "Defect on Linux" template when filing a new one. do not skip this step, i'm begging 🥺

---

💜 AUTHOR 💜

The Chromium team — <http://www.chromium.org>

---

and that's the whole page, bestie!! it's from chromium-browser(1) in the USER COMMANDS section, and it's signed off by chromium-browser(1) at the bottom like a little signature 💖 slay, go browse something, you've earned it ✨🦋🌸