Free tools Windows power users keep installed
One-click scans. No signup required.
On Ubuntu 16.04 LTS and later, install the maintained Chromium package with sudo snap install chromium. On CentOS, first identify the release, enable EPEL, install and enable snapd, create the /snap link, then run the same Snap command. The exact EPEL command differs between CentOS 7 and CentOS 8/9 Stream.
Choose the right installation path
Chromium is the open-source browser project behind Chrome. The supported command-line path in the current Canonical and Snap documentation is Snap. Ubuntu normally has Snap ready to use; CentOS requires repository and daemon setup first.
| System | Recommended path | Prerequisites | Update behavior |
|---|---|---|---|
| Ubuntu 16.04 LTS or later | sudo snap install chromium |
Snap is installed on a standard Ubuntu system; some flavors require snapd |
Snap packages update automatically |
| CentOS 8, 8 Stream, 9 Stream | EPEL + snapd + Snap Chromium |
dnf, EPEL, enabled snapd.socket, and the classic Snap link |
Snap packages update automatically |
| CentOS 7 (7.6 or later for snapd support) | EPEL + snapd + Snap Chromium |
yum, EPEL, enabled snapd.socket, and the classic Snap link |
Snap packages update automatically |
| Specific test or build revision | Upstream standalone Chromium archive | Manual download and execution | No package-managed update path; old builds may lack current security fixes |
The Fedora Project package index also lists Chromium for EPEL 8, EPEL 9 and EPEL 10 variants. That does not make dnf install chromium or yum install chromium a universal CentOS instruction: repository enablement, package names, dependencies and compatibility depend on the exact Enterprise Linux release.
Install Chromium on Ubuntu
Standard Ubuntu installation
On Ubuntu 16.04 LTS and later, Canonical documents Snap as already installed on the standard system. Open a terminal and run:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
sudo snap install chromiumSnap downloads the Chromium package and registers the chromium command. Start it from the desktop application menu, or run:
chromiumIf your desktop menu does not refresh immediately, start a new login session. The Snap package is maintained through the Snap Store and receives automatic updates.
When Snap is missing
Some Ubuntu flavors do not include Snap by default. Install the daemon with the documented APT commands:
sudo apt update
sudo apt install snapdAfter installation, log out and back in, or restart the computer, so the Snap paths are updated. Then install Chromium:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchsudo snap install chromiumCheck that Snap sees the package:
snap list chromiumIf the command reports a package row containing Chromium, the installation is complete.
Why an APT command can lead to Snap
Ubuntu’s Chromium delivery is Snap-based in the documented current workflow. Therefore, an APT attempt may install or direct you to a Snap package rather than unpacking a traditional .deb browser. Use the explicit Snap command when you want the supported Ubuntu route, and do not assume that an identical APT command behaves the same on every Ubuntu release or flavor.
Install Chromium on CentOS
1. Identify the CentOS release
Repository instructions differ by major version. Check the system before changing repositories:
cat /etc/centos-releaseLook for CentOS 7, CentOS 8, CentOS 8 Stream or CentOS 9 Stream. The Snap daemon documentation lists CentOS 7, 8, 8 Stream and 9 Stream as supported, with CentOS 7 support beginning at 7.6.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →2. Enable EPEL
For CentOS 8, CentOS 8 Stream and CentOS 9 Stream, use dnf:
sudo dnf install epel-release
sudo dnf upgradeFor CentOS 7, use yum:
sudo yum install epel-releaseEPEL dependency versions can occasionally be out of sync with the base system. If a later step reports a missing package, verify that the EPEL repository matches your CentOS major version instead of mixing repositories from another release.
3. Install and enable snapd
The documented Snap Store sequence uses yum for the daemon installation on the CentOS variants:
sudo yum install snapd
sudo systemctl enable --now snapd.socketThe symbolic link enables classic Snap support. Confirm that the socket is active:
systemctl is-active snapd.socketAn output of active means the daemon is listening. Log out and back in, or restart, so the Snap paths are available to your session.
4. Install and launch Chromium
sudo snap install chromiumLaunch from the desktop menu or run:
chromiumVerify the installed Snap:
snap list chromiumCentOS RPM packages: when to investigate them
Chromium appears in EPEL package indexes for EPEL 8, EPEL 9 and EPEL 10. Availability is not identical to compatibility. Before choosing an RPM route, inspect the enabled repositories and package metadata for the actual machine:
sudo dnf repolist
dnf info chromiumOn CentOS 7, use the equivalent yum metadata command:
sudo yum repolist
yum info chromiumIf metadata shows no compatible package, use the documented Snap procedure rather than forcing an RPM from another Enterprise Linux release. Mixing repositories can create dependency conflicts and leave the browser without a dependable update path.
Standalone Chromium archives: a specialized fallback
The Chromium project provides a Linux archive workflow: choose Linux, select a build number, download the ZIP archive and run its executable. This is useful when you need a particular revision for testing, automation or build investigation.
It is not the normal general-purpose installation method. Upstream describes these builds as best-effort, and an arbitrary revision does not necessarily correspond to a user-facing Chrome release. Standalone builds do not follow the Snap update mechanism, and old revisions do not receive current security fixes. For an everyday workstation, use the distribution-supported Snap or a verified compatible repository package instead.
Rank #4
Verify the installation and updates
Check the executable
chromium --versionThis prints the browser version selected by your shell. On a Snap installation, also check the package record:
snap list chromiumCheck Snap refresh status
snap refresh --listIf no refresh is listed, there is currently nothing pending. Snap handles routine updates; you do not need to download a new Chromium archive for each release.
Recommended Free Tools
Confirm which binary your shell uses
command -v chromium
readlink -f "$(command -v chromium)"The resolved path helps distinguish a Snap installation from an older RPM or manually unpacked executable when several installations have been attempted.
Troubleshooting common failures
snap: command not found on Ubuntu
Install snapd with APT, then log out and back in or restart:
sudo apt update
sudo apt install snapdRun snap version after the new session and retry the Chromium command.
snap: command not found on CentOS
The daemon is not installed or the session has not picked up the new path. Confirm EPEL, install snapd, enable its socket, create /snap, then start a new login session:
Best Value
sudo yum install snapd
sudo systemctl enable --now snapd.socket
sudo ln -s /var/lib/snapd/snap /snapSnap cannot communicate with the daemon
Check the socket and start it if necessary:
systemctl status snapd.socket
sudo systemctl enable --now snapd.socketRetry only after the status shows the socket is active.
The /snap link already exists
Do not replace a working link blindly. Inspect it:
ls -ld /snap
readlink -f /snapIf it points to /var/lib/snapd/snap, continue with the installation. If it points elsewhere, correct the path only after confirming that no other Snap configuration depends on it.
EPEL reports a missing or conflicting dependency
Read the error's repository and version names. Confirm the output of cat /etc/centos-release, enable the matching EPEL major version, and refresh metadata. Do not install an EPEL package built for a different CentOS stream merely to satisfy one dependency.
Chromium installs but will not start
Run it from a terminal to capture the first error:
chromiumThen check the Snap package and daemon state:
snap list chromium
systemctl is-active snapd.socketA stale manually downloaded build can also shadow the Snap command. Use command -v chromium and remove or rename the unintended executable only after identifying its package owner.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The browser is not the revision you expected
Snap follows the maintained channel rather than an arbitrary upstream revision. If a test requires a fixed build number, use the upstream archive workflow and document the revision, while accepting that old builds may not include current security fixes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability and cost considerations
- Maintenance: Snap provides automatic package refreshes; a standalone archive leaves update management to you.
- Compatibility: Ubuntu's prerequisite is usually already present, while CentOS requires EPEL,
snapd, a running socket and the classic link. - Repository risk: EPEL package availability varies by Enterprise Linux major version. Inspect metadata before writing automation that assumes a package exists.
- Reproducibility: A pinned standalone build can help testing, but record its build number and isolate it from the system browser.
- Security: Avoid relying on old Chromium archives for normal browsing because upstream warns that old builds lack current security fixes.
Or skip the browser setup
If your goal is to obtain screenshots rather than operate a desktop browser, ScreenshotNeo provides a website screenshot API and MCP server. One request returns a PNG, JPEG, WebP or PDF, so there is no Chromium installation to maintain in your application environment.
cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for parameters and response headers. Before capture, it can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the page verdict and billing status with X-Page-Verdict and X-Billed headers. Its MCP server exposes take_screenshot, get_page_info and capture_pdf for Claude, Cursor and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Frequently Asked Questions
How can I tell whether Chromium came from Snap or an RPM?
Run command -v chromium, readlink -f "$(command -v chromium)" and snap list chromium. The resolved path and Snap record identify the installation source.
Can I keep a fixed Chromium revision for automated tests?
Yes. Use the upstream Linux archive workflow, record its build number and treat it as a separate test binary. Upstream describes these builds as best-effort, and old revisions may not contain current security fixes.
Does CentOS 7 support the Snap daemon?
The documented support starts at CentOS 7.6. Confirm the exact release with cat /etc/centos-release before installing EPEL and snapd.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
