Install w3m with Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• w3m
• w3mman

Project history

Akinori Ito's own history traces w3m back to an earlier pager called fm, written before 1991 for inspecting very long debug-output lines without wrapping. After Ito learned HTML and HTTP, he modified fm into a simple web browser; the first version of w3m was released at the beginning of 1995.

The name comes from the Japanese phrase 'WWW wo miru', meaning roughly 'see the WWW', inheriting the naming pattern from fm, or 'File wo miru'. The project was originally motivated by the desire to glance quickly at web pages without starting a heavyweight graphical browser, while still keeping the pager behavior that made fm useful.

w3m's major late-1990s transition came when Ito returned to the project in 1998 and implemented a table renderer and forms. The history page describes this as w3m being reborn as a practical web browser, because table-heavy pages had become common and incomplete table rendering made many pages unusable in text mode.

Adoption history

The official SourceForge project was registered in November 2001, and the project page summarizes w3m as both a pager and text-based browser. Its FAQ also documents portability across Unix variants, OS/2, and Windows via Cygwin in the early era, reflecting the tool's spread among terminal-heavy users and ports collections.

How it is used

w3m is used as a terminal browser for local files and web pages, as a pager for HTML or text passed as files or standard input, and as a scriptable formatter that can turn HTML into readable terminal output. Its FAQ notes that invoking w3m without arguments exits because it behaves as a pager; normal inputs are a filename, URL, pipe, bookmark view, visual startup, or home URL.

Configuration is part of its Unix culture: the FAQ names `~/.w3m/config` as the configuration file, and w3m users commonly tune key bindings, color, proxies, external viewers, and editor integration for text-only workflows.

Why package nerds care

w3m matters because it occupies the intersection of pager, browser, and HTML formatter. Compared with Lynx, its project history emphasized table rendering, frame handling by conversion to tables, standard-input use, small size, and fast startup. That made it a favorite tool for reading documentation, testing HTML, browsing from remote shells, and automating text rendering of web content.

Timeline

• Before 1991: Ito wrote the fm pager for inspecting long debug-output lines.
• Beginning of 1995: The first version of w3m was released.
• 1998: Ito resumed development and implemented table rendering and forms.
• 1999: The English history page was published, explaining w3m's origin and design tradeoffs.
• 2001: The w3m SourceForge project was registered.
• 2020s: Maintenance continues from the source repository referenced by current curation.

Related projects

• w3m is historically related to fm, its pager ancestor, and often compared with Lynx, the older text-mode browser. It also depends historically on Boehm GC, which Ito credited as important for implementing tables and forms.

Sources

• https://git.sr.ht/~rkta/w3m
• https://sourceforge.net/projects/w3m/
• https://w3m.sourceforge.net/FAQ
• https://w3m.sourceforge.net/MANUAL
• https://w3m.sourceforge.net/STORY