This guide walks you through installing WPS Office on AlmaLinux 9 without spending a dime on Microsoft Office, covering every prerequisite and common stumbling block. It begins by updating the system, adding Development Tools and essential X11 libraries before pulling the official RPM from WPS’s website. Once the package is installed—adding EPEL or rpmfusion if needed—you can launch the application, adjust fonts, or choose Flatpak for a sandboxed experience. The final section highlights typical pitfalls such as missing libraries or architecture mismatches so you can avoid them before they trip you up.

How to Install WPS Office on AlmaLinux 9

If you’ve got an AlmaLinux 9 box and want a Microsoft‑Office‑like experience without the price tag, this guide shows you exactly how to get WPS Office up and running. You’ll learn which packages to pull in first, where to grab the installer from, and what to do if dependencies bite back.

Step 1 – Make sure your system is ready

• Update everything so you don’t run into version mismatches later:

`sudo dnf update -y`

A fresh kernel and libraries give WPS a smoother ride.

• Install the “Development Tools” group; it pulls in GCC, make, etc., which are handy if any of the RPMs need compiling for missing libs.

`sudo dnf groupinstall "Development Tools" -y`

Step 2 – Pull in required libraries

WPS Office relies on a handful of shared libs that don’t ship by default on AlmaLinux minimal installs:

sudo dnf install libXcomposite libXi libXrender libXcursor \
    libXrandr libXss libXtst -y

> I've seen this happen after a fresh AlmaLinux 9 install – the GUI just hangs when you try to launch WPS.

Step 3 – Download the RPM from WPS’ site

Go straight to the official page for the Linux build. At the time of writing, the link points to a single‑file RPM:

wget https://wdl1.pcfg.wpscdn.com/wpsdl/online/desktop/linux/WPSOffice-11.2.0.10270-x86_64.rpm

If that URL changes, you’ll need to grab the latest from < https://www.wps.com/download/> and look for “Linux (RPM).”

Step 4 – Install the package with DNF

Run:

sudo dnf install ./WPSOffice-11.2.0.10270-x86_64.rpm

DNF will resolve dependencies automatically, but if it complains about missing packages, add the “rpmfusion” or “epel” repos first. For example:

sudo dnf install epel-release -y
sudo dnf install rpmfusion-free-release noarch -y

> On a server that only had the base repo enabled, I hit “Failed to resolve dependencies for WPSOffice‑…” and adding EPEL fixed it instantly.

Step 5 – Launch and tweak

Start WPS Office from the application menu or via terminal:

wps

The first run will create a config directory in your home folder. If you’re on a desktop environment that doesn’t auto‑detect fonts, add the following to make everything look crisp:

sudo dnf install fontconfig

Optional – Use Flatpak for isolation

If you prefer sandboxing or want an easier upgrade path, install the Flatpak package instead of the RPM:

sudo dnf install flatpak -y
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub com.wps.Office

This method keeps WPS in a self‑contained environment, so system libraries don’t get clobbered.

Common pitfalls to avoid

• Missing X11 libraries – If you see “cannot open shared object file: No such file or directory,” double‑check the libX* list above.
• 32‑bit vs 64‑bit mismatch – Make sure you download the x86_64 build; the 32‑bit version will fail on a default AlmaLinux 9 install.

That’s it. WPS Office should now be ready to use alongside LibreOffice or Microsoft Office files, all running smoothly on your AlmaLinux 9 machine.