WPS Linux means running WPS Office—Writer, Spreadsheet, Presentation, and PDF tools—natively on a desktop Linux system such as Ubuntu or Linux Mint. The shortest reliable path is: download the current package from the official WPS Linux page, install that local file with your package manager, then launch Writer once and open a DOCX or XLSX file to confirm success.
Critical prerequisites: you need a 64-bit (x86_64) desktop install for the standard Deb/Rpm builds, sudo rights, and a GUI session. Do not force an old 32-bit package or an ARM build onto the wrong CPU. Success looks like WPS appearing in your app menu and opening Microsoft Office–compatible files without a terminal error.
If something fails, jump to the matching branch below: install dependency errors, launch failures such as missing libcrypto.so.1.1, missing-font dialogs, or a broken uninstall.

For a broader must-have software list on Ubuntu, see best Linux apps.
What WPS Linux Is (and Is Not)
WPS Office for Linux is Kingsoft’s free desktop suite for common document, spreadsheet, presentation, and PDF work. It is built for desktop environments on major distributions—Ubuntu and Linux Mint are explicitly called out on the official site—not as a headless server service.
It is also not installed from Ubuntu’s default apt repository as an always-current official package. Community Snap/Flatpak builds may appear in software stores, but they are not the vendor’s documented default. For accuracy and updates, use the Deb or Rpm files published on the official WPS Linux download page.
Check Architecture and Distro Before You Download
Run:
uname -m
| Result | What to download |
|---|---|
x86_64 | Standard 64-bit Deb (Debian/Ubuntu/Mint) or Rpm (Fedora/RHEL-like) from the official page |
aarch64 / ARM | Use the ARM package only if the vendor currently offers one for your channel (for example via WPS 365 where noted); do not install an x64 Deb on ARM |
32-bit (i686 / i386) | Current WPS Linux no longer ships a 32-bit build; upgrade hardware/OS path instead of forcing legacy packages |
Also confirm you are on a desktop session with a display. Desktop GUI office suites are not a supported “install and run over SSH only” workflow unless the vendor documents a headless mode (WPS Linux does not).
Download the Official Package Only
Open the official page: WPS Office for Linux.
Choose Deb Package for Ubuntu, Debian, Linux Mint, Pop!_OS, and similar systems.
Choose Rpm Package for Fedora, RHEL-like, openSUSE, and similar systems.
Save the file (typically under
~/Downloads). Note the exact filename—version numbers change over time.
Do not use old community mirror links (for example stale kdl / “WPS Community” Alpha URLs from years-old forum posts) as your default installer. Those packages and dependency assumptions are often outdated. Prefer the live official download page every time.
Install WPS on Ubuntu / Debian with the Deb File
This is the primary workflow for most “wps linux” searches.
Open a terminal and move to the download folder:
cd ~/Downloads ls *.deb
Install the local package file (path required). Replace the filename with the exact file you downloaded:
sudo apt install ./wps-office_VERSION_amd64.deb
./ matters. That command installs a file on disk. It is not the same as sudo apt install wps-office, which looks for a repository package name and may fail or pull an unexpected source.
Alternative equivalent:
sudo dpkg -i ./wps-office_VERSION_amd64.deb sudo apt-get install -f
Use apt-get install -f only if dpkg reports missing dependencies.
Confirm the package is present:
dpkg -l wps-office
Optional GUI path
In your file manager, open the downloaded .deb, choose your distro’s software installer, and click Install. Enter your password when prompted. Functionally this is the same local-package install.
Short Branch: Install with the Rpm Package
On Fedora or other Rpm-based desktops:
cd ~/Downloads sudo dnf install ./wps-office-VERSION.x86_64.rpm
Or, where dnf is unavailable:
sudo rpm -ivh ./wps-office-VERSION.x86_64.rpm
Again, install the local file you downloaded. Do not treat random third-party repos, PPAs, Snap names, or Flatpak refs as “official” unless Kingsoft currently publishes them.
Launch WPS and Verify Success
After install:
Open your app menu and search for WPS Writer, WPS Spreadsheets, or WPS Presentation.
Or start from a terminal:
wps
(Spreadsheet / Presentation launchers may be et / wpp depending on the build; if a command is missing, use the menu entry from the installed package rather than inventing names.)
Open a sample
.docx,.xlsx, or.pptxfile.Save a small test file to confirm write access to your home folder.
If the apps appear and files open, your WPS Linux install is complete.
Fix Common Install and Launch Problems
Work through these only when you hit the matching symptom. Do not install random fonts or libraries “just in case.”
1) Dependency errors during Deb install
If apt/dpkg lists missing packages, finish dependency repair:
sudo apt-get install -f
Then retry the local Deb install. Very old community tutorials that force libpng12 were aimed at obsolete Alpha builds; start from the current official package instead of those legacy steps.
2) Launch error: libcrypto.so.1.1 / libssl.so.1.1
On some Ubuntu 22.04-era setups, older WPS builds failed with OpenSSL 1.1 library errors because the system defaulted to OpenSSL 3.
Order of action:
Re-download and install the latest official Deb from wps.com/office/linux—many launch bugs are version-specific.
If the terminal still shows the exact missing
libcrypto.so.1.1/libssl.so.1.1error, install the matching Ubuntulibssl1.1package for your architecture from Ubuntu’s package archive (amd64 vs arm64 must matchuname -m). Use the exact archive filename you download; do not guess.Relaunch without
sudo. Running WPS as root is not the normal desktop workflow and can hide permission problems.
3) Font warning dialogs
If—and only if—WPS shows a missing-font warning, note the font names in the dialog. Install those fonts through your distro’s font packages or vendor guidance. Do not treat unofficial GitHub font packs as a guaranteed official fix; they are community workarounds with their own licensing.
Flatpak installs are more likely to surface font sandbox issues; the official Deb/Rpm path usually avoids that class of problem.
4) Wrong architecture or discontinued 32-bit builds
If install rejects the package, confirm uname -m and download the matching vendor build. Current mainstream Linux packages are 64-bit x86_64; 32-bit Linux packages are no longer the supported path.
5) File associations look wrong after install
Some users report WPS rewriting MIME associations for Office documents. If that happens, reset associations in your desktop settings, or remove the override file WPS created under your user MIME config and refresh the MIME database—only after you confirm that override exists. Prefer fixing associations over reinstalling first.
Uninstall WPS Office Cleanly
For Deb-based systems installed as package wps-office:
sudo apt remove wps-office
To also remove system configuration packages where applicable:
sudo apt purge wps-office
Very old Kingsoft-branded packages used different names (for example kingsoft-office in legacy threads). Check what you actually installed:
dpkg -l '*wps*' '*kingsoft*'
Then remove the exact package name shown.
For Rpm/dnf systems:
sudo dnf remove wps-office
User settings may remain under your home directory (for example Kingsoft/WPS config folders). Delete those only if you want a full personal reset; that step removes preferences and is optional.
After Install: Use WPS for Everyday Office Files
Once WPS Linux is running, use it as your daily editor for DOCX, XLSX, PPTX, and PDF workflows on Ubuntu or other supported desktops. Open existing Microsoft Office files, edit, and export without leaving Linux.
Prefer the latest build from the official WPS Linux download page whenever you reinstall or update, so you stay on a current Deb/Rpm package rather than an abandoned forum mirror.
FAQ
Is WPS Office free on Linux?
Yes. The Linux desktop suite is offered as a free download from the official WPS Linux page. Some advanced or account-tied features may differ by platform and account status; check the product notes for your build.
Should I install from Snap or Flatpak instead?
You can, if your distro ships those builds, but they are not the vendor’s primary documented channel. For supportability, prefer Deb/Rpm from wps.com/office/linux.
Can I install WPS with a plain apt install wps-office?
Only if a repository you trust actually provides that package. The official path is downloading a Deb/Rpm and installing the local file with apt install ./file.deb or the Rpm equivalent.
Does WPS Linux still support 32-bit PCs?
No current official 32-bit Linux package is offered. Use a 64-bit system and the matching x64 package.
WPS only starts with sudo. What now?
That usually points to a library or permission problem, not a requirement to run as root. Update to the latest official package first; if you still see OpenSSL 1.1 library errors, fix the missing library for your architecture, then launch as your normal user.
How do I update later?
Download the newest Deb/Rpm from the official page and install it over the existing package with the same local-file method.




