How to Install WPS Office via Command Line on Ubuntu

To install WPS Office via the command line on Ubuntu, download the official Deb package from the WPS Linux page, then install that local file with APT. Ask Ubuntu threads such as “How to install wps office via terminal?” exist because graphical installers freeze, hang without useful logs, or leave dependency errors that Software Center never shows clearly. The durable vendor package for Debian-family systems is the Deb download—not a fictional WPS APT repository and not an expired mirror copied from an old community answer.

Shortest reliable path: confirm your CPU architecture, download the Deb from wps.com/office/linux, run sudo apt install ./exact-file.deb, repair unmet dependencies only as APT reports them, then launch Writer from a graphical desktop session. Success means dpkg -l wps-office shows status ii and a confirmed launcher opens a sample document.

What Ask Ubuntu Users Were Trying to Solve

The original terminal-install questions usually share three goals. First, avoid a GUI download flow that freezes mid-install. Second, keep a path that can be repeated later when a newer build appears. Third, understand whether “third-party Deb files from separate locations” are safe. Those goals are still correct. What changed is the safe source of the Deb: versioned wget URLs that once pointed at community or cache hosts routinely break after each WPS release, so modern guidance must treat the official Linux download page as the entry point and treat copied old URLs as historical examples only.

A second cluster of command-line threads starts after someone follows an old dpkg -i recipe and hits a missing library—classically libpng12-0 on older WPS builds. Then apt-get install -f offers to remove wps-office instead of finishing the install. That sequence is documented in “How to install WPS Office via Command Line” and related dependency posts. It is APT protecting a half-configured package, not proof that WPS cannot be installed with the terminal.

Confirm Architecture Before You Touch Any Deb

Open a terminal and check the machine first. Architecture mistakes are not theoretical: Kubuntu and Ubuntu reports of “cannot satisfy dependencies” and later “package needs to be reinstalled, but I can’t find an archive for it” often begin with the wrong Deb.

uname -m
dpkg --print-architecture

On a typical modern Ubuntu PC you should see x86_64 and amd64. After you download the Deb, inspect metadata—do not trust the filename alone:

dpkg-deb -I ~/Downloads/wps-office_12.1.0.xxxxx_amd64.deb | grep -E 'Package|Version|Architecture|Depends'

Replace the placeholder with your exact filename. Expected result: Package: wps-office and an Architecture that matches dpkg --print-architecture. If the official download page does not offer a matching build for your device (for example some ARM machines), stop. Forcing the wrong Deb creates the broken reinstall loops people report when cleanup commands can no longer find an archive for wps-office:i386 or a similar mismatched package.

Download From the Official Linux Page—Not Stale Direct Links

Go to the vendor Linux page and choose Deb Package. That page is the durable entry point when versioned CDN URLs change. High-scoring older answers literally warned that wget links break at every version change and pointed readers back to a download page—the same caution still applies, only the canonical page for current packages is the official WPS Linux URL above.

ls -lh ~/Downloads/wps-office*.deb

Copy the exact name. Prefer that exact filename in later commands. Broad wildcards such as *.deb are unsafe when Downloads contains more than one Deb file. If you insist on a terminal download, only paste a URL you personally copied from the current official page—do not reuse multi-year-old community wget examples as your default install method.

Install With APT Using a Local File Path

This distinction prevents the most common misunderstanding when people search for “install via command line” or “via terminal”:

• Repository lookup: sudo apt install wps-office — looks for a package name in configured repositories

• Local file: sudo apt install ./wps-office_12.1.0.xxxxx_amd64.deb — installs the Deb you downloaded

For the official Deb workflow, use the local form:

cd ~/Downloads
sudo apt update
sudo apt install ./wps-office_12.1.0.xxxxx_amd64.deb

Expected result: APT schedules wps-office for installation, may pull dependencies from Ubuntu repositories, and finishes without leaving the package unconfigured. The leading ./ is required so APT treats the argument as a file path instead of a repository package name.

If you already used the low-level installer:

sudo dpkg -i ./wps-office_12.1.0.xxxxx_amd64.deb

dpkg unpacks the package but does not resolve missing dependencies. When it prints “dependency problems prevent configuration,” do not force the package with reckless flags. Move to repair.

When apt --fix-broken Tries to Remove WPS Office

Users following older command-line guides often hit this exact movie: dpkg -i fails on a missing library, then sudo apt-get install -f proposes removing wps-office to “correct” the system. If you answer yes, you are back to zero and the Deb appears to have “failed mysteriously.” Instead:

sudo apt --fix-broken install

Read the named dependency in the error. On modern official Debs, many dependencies resolve from Ubuntu’s own repositories during the APT local install. On very old WPS packages, the named library may be obsolete on newer Ubuntu releases—historically libpng12-0. Treat that as a version-era limitation of that old Deb, not a universal requirement for every Ubuntu release today. Prefer downloading a current official Deb from the WPS Linux page and installing that local file again.

sudo dpkg --configure -a
dpkg -l wps-office

A healthy install shows status ii. Only install a specifically named missing package when APT prints that name and your repositories still provide it. Do not invent a WPS PPA so that apt upgrade will “magically” track future releases.

Fonts Warnings Are Not the Same as a Failed Install

Separate Ask Ubuntu reports describe formula-symbol font warnings after Flatpak or other channels. Those dialogs are annoying, but they are not the same failure as an unconfigured Deb. If a formula-symbol warning appears after a successful Deb install, read the exact font name in the dialog. Do not uninstall the suite to chase fonts, and do not assume a generic “install all fonts” package fixes every warning. Confirm first that Writer actually opens and that ordinary documents load.

Launch and Verify on a Graphical Desktop

WPS Office is GUI software. Launch it from a normal desktop session, not a headless server console.

dpkg -L wps-office | grep -E '/usr/bin/|applications'
command -v wps
command -v et
command -v wpp

Executable names and install paths can vary by build. Treat wps, et, and wpp as build-dependent until dpkg -L or command -v confirms them. If a confirmed command exists:

wps

Expected result: Writer opens. Also open the app menu, search for WPS, and open a sample .docx file. Save a trivial edit. That is the real acceptance test—package status alone is not enough if a launcher is missing or points to a half-removed package.

Command-Line Failure Triage (Non-Destructive First)

Architecture mismatch or leftover i386 package

Compare architectures, then remove the mismatched package before installing the correct Deb:

sudo apt remove wps-office
sudo dpkg --remove --force-remove-reinstreq wps-office:i386

Only use force-remove variants when dpkg reports a broken reinstall loop and normal remove fails. Then install the matching official amd64 Deb.

Unmet dependencies

sudo apt --fix-broken install
sudo apt install ./wps-office_12.1.0.xxxxx_amd64.deb

Command not found after install

dpkg -l wps-office
dpkg -L wps-office | grep /usr/bin/

Reinstall the exact Deb if the package is missing or half-installed. If binaries exist, open a new terminal and retry the confirmed name. Desktop menu caches sometimes need a logout.

Installs but will not open

Start from the terminal so stderr is visible, then:

sudo dpkg --configure -a
sudo apt --fix-broken install

If the process exits immediately with no dialog, capture the terminal output before trying unrelated “fix” tips from unrelated Wine or Flatpak threads.

How This Differs From Snap Command-Line Install

Some terminal answers recommend sudo snap install wps-office plus sudo snap connect wps-office:removable-media. That is a valid Ubuntu Snap Store path, but it is not the same as installing the official Deb with APT. Snap auto-refresh behavior and confinement rules differ. If your keyword intent is command-line Deb install, stay on the Deb workflow; if you intentionally want Snap, use Snap commands end-to-end and do not mix both packages without a reason.

FAQ

Is command-line install different from “via terminal”?

No meaningful difference on Ubuntu—both mean installing the official Deb with shell commands rather than only a GUI click-through.

Can I run sudo apt install wps-office with no file path?

Not from Ubuntu’s default repositories. That form is a repository lookup. Use sudo apt install ./exact-file.deb after downloading the official Deb.

Should I add a WPS PPA so apt upgrade works forever?

No. Do not invent or trust unverified PPAs for this install. Update later by installing a newer official Deb the same way.

Do I still need a separate fonts Deb from old answers?

Older guides bundled a fonts package and separate community font downloads. Current installs should follow what your downloaded Deb and error dialogs actually require—do not install random font packages prophylactically.

Does this cover Windows or WSL?

No. This workflow is for Ubuntu/Debian-style Linux desktops installing a Deb package on a graphical session.

Free Office Download

• Use Word, Excel, and PPT for FREE, No Ads.

• Edit PDF files with the powerful PDF toolkit.

• Microsoft-like interface. Easy to learn. 100% Compatibility.

• Boost your productivity with WPS's abundant free Word, Excel, PPT, and CV templates.

Free Download

100% secure