man page - Wikipedia https://en.wikipedia.

org/wiki/Man_page

man page
A man page (short for manual page) is a form of software
documentation found on Unix and Unix-like operating systems.
Topics covered include programs, system libraries, system calls, and
sometimes local system details. The local host administrators can
create and install manual pages associated with the specific host. A
manual end user may invoke a documentation page by issuing the
man command followed by the name of the item for which they want
the documentation. These manual pages are typically requested by
end users, programmers and administrators doing real time work but
can also be formatted for printing.

By default, man typically uses a formatting program such as nroff

with a macro package or mandoc, and also a terminal pager program
such as more or less to display its output on the user's screen.

Man pages are often referred to as an online form of software

documentation,[1] even though the man command does not require
internet access. The environment variable MANPATH often specifies The man page for the sed utility, as
a list of directory paths to search for the various documentation pages. seen in various Linux distributions.

Manual pages date back to the times when printed documentation was
the norm.

History
Before Unix (e.g., GCOS), documentation was printed pages,
available on the premises to users (staff, students...), organized into
steel binders, locked together in one monolithic steel reading rack,
bolted to a table or counter, with pages organized for modular
information updates, replacement, errata, and addenda.

In the first two years of the history of Unix, no documentation existed.

[2] The Unix Programmer's Manual (http://man.cat-v.org/unix-1st/)
was first published on November 3, 1971. The first actual man pages
were written by Dennis Ritchie and Ken Thompson at the insistence
of their manager Doug McIlroy in 1971. Aside from the man pages,
the Programmer's Manual also accumulated a set of short papers,
some of them tutorials (e.g. for general Unix usage, the C xman, an early X11 application for
programming language, and tools such as Yacc), and others more viewing manual pages
detailed descriptions of operating system features. The printed version

1 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

of the manual initially fit into a single binder, but as of PWB/UNIX

and the 7th Edition of Research Unix, it was split into two volumes
with the printed man pages forming Volume 1.[3]

Later versions of the documentation imitated the first man pages'

terseness. Ritchie added a "How to get started" section to the Third
Edition introduction, and Lorinda Cherry provided the "Purple Card"
pocket reference for the Sixth and Seventh Editions.[2] Versions of the OpenBSD section 8 intro man page,
software were named after the revision of the manual; the seventh displaying in a text console
edition of the Unix Programmer's Manual, for example, came with
the 7th Edition or Version 7 of Unix.[4]

For the Fourth Edition the man pages were formatted using the troff typesetting package[2] and its set of -
man macros (which were completely revised between the Sixth and Seventh Editions of the Manual,[3] but
have since not drastically changed). At the time, the availability of online documentation through the manual
page system was regarded as a great advance. To this day, virtually every Unix command line application
comes with a man page, and many Unix users perceive a program's lack of man pages as a sign of low quality
or incompleteness. Indeed, some projects, such as Debian, go out of their way to write man pages for
programs lacking one. The modern descendants of 4.4BSD also distribute man pages as one of the primary
forms of system documentation (having replaced the old -man macros with the newer -mdoc).

There was a hidden Easter egg in the man-db version of the man command that would cause the command to
return "gimme gimme gimme" when run at 00:30 (a reference to the ABBA song Gimme! Gimme! Gimme!
(A Man After Midnight). It was introduced in 2011[5] but first restricted[6] and then removed in 2017[7] after
finally being found.[8]

Formatting
The default format of man pages is troff, with either the macro
package man (appearance oriented) or mdoc (semantic oriented). This
makes it possible to typeset a man page into PostScript, PDF, and
various other formats for viewing or printing.

Some Unix systems have a package for the man2html command,

which enables users to browse their man pages using an HTML
browser. Systems with groff and man-db should use the higher-quality
native HTML output (man --html) instead. The GNU Emacs
program WoMan (from "WithOut man") allows to browse man pages Part of the FreeBSD man(1) manual
from the editor.[9] page, typeset into PDF format

In 2010, OpenBSD deprecated troff for formatting man pages in

favour of mandoc, a specialised compiler/formatter for man pages with native support for output in
PostScript, HTML, XHTML, and the terminal. It is meant to only support a subset of troff used in manual
pages, specifically those using mdoc macros.

2 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

Online services
Quite a few websites offer online access to manual pages from various Unix-like systems.

In February 2013, the BSD community saw a new open source mdoc.su (http://mdoc.su/) service launched,
which unified and shortened access to the man.cgi scripts of the major modern BSD projects through a
unique nginx-based deterministic URL shortening service for the *BSD man pages.[10][11][12]

For Linux, a man7.org service has been set up to serve manuals specific to the system.[13] A ManKier service
provides a wider selection, and integrates the TLDR pages too.[14]

Command usage
To read a manual page for a Unix command, a user can type:

man <command_name>

Pages are traditionally referred to using the notation "name(section)": for example, ftp(1) (https://w
ww.freebsd.org/cgi/man.cgi?query=ftp&sektion=1). The section refers to different ways
the topic might be referenced - for example, as a system call, or a shell (command line) command or package,
or a package's configuration file, or as a coding construct / header.

The same page name may appear in more than one section of the manual, such as when the names of system
calls, user commands, or macro packages coincide. Examples are man(1) (https://www.mankier.c
om/1/man) and man(7) (https://www.mankier.com/7/man), or exit(2) (https://man
ned.org/exit.2) and exit(3) (https://manned.org/exit.3). The syntax for accessing
the non-default manual section varies between different man implementations.

On Solaris and illumos, for example, the syntax for reading printf(3C) (https://docs.oracle.c
om/cd/E88353_01/html/E37843/printf-3c.html) is:

man -s 3c printf

On Linux and BSD derivatives the same invocation would be:

man 3 printf

which searches for printf in section 3 of the man pages. The actual file name likely includes the section.
Continuing this example, printf.3.gz would be a compressed manual page file in section 3 for printf.

Manual sections

3 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

The manual is generally split into eight numbered sections. Most systems today (e.g. BSD,[15] macOS, Linux,
[16] and Solaris 11.4) inherit the numbering scheme used by Research Unix.[17][18] While System V uses a

different order:[19]

Common System V Description

1 1 General commands

2 2 System calls

3 3 Library functions, covering in particular the C standard library

4 7 Special �iles (usually devices, those found in /dev) and drivers

5 4 File formats and conventions

6 6 Games and screensavers

7 5 Miscellaneous

8 1M System administration commands and daemons

POSIX APIs are present in both sections 2 and 3, where section 2 contains APIs that are implemented as
system calls and section 3 contains APIs that are implemented as library routines.

On some systems, additional sections may be included such as:

Section Description

0 C library header �iles (Unix v6)

9 Kernel routines (FreeBSD, SVR4, Linux)[18][15]

l LAPACK library functions[20]

n Tcl/Tk commands

x The X Window System

Some sections are further subdivided by means of a suffix; for example, in some systems, section 3C is for C
library calls, 3M is for the math library, and so on. A consequence of this is that section 8 (system
administration commands) is sometimes relegated to the 1M subsection of the main commands section.
Some subsection suffixes have a general meaning across sections:

Subsection Description

p POSIX speci�ications

x X Window System documentation

(Section 3 tends to be the exception with the many suffixes for different languages.)

Some versions of man cache the formatted versions of the last several pages viewed. One form is the cat
page, simply piped to the pager for display.

4 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

Layout
All man pages follow a common layout that is optimized for presentation on a simple ASCII text display,
possibly without any form of highlighting or font control. Sections present may include:
[21]:MANUAL STRUCTURE

NAME
The name of the command or function, followed by a one-line description of what it does.
SYNOPSIS
In the case of a command, a formal description of how to run it and what command line options it
takes. For program functions, a list of the parameters the function takes and which header �ile
contains its declaration.
DESCRIPTION
A textual description of the functioning of the command or function. For programs, this section
o�en includes explanations of available command line options.
EXAMPLES
Some examples of common usage.
SEE ALSO
A list of related commands or functions.

Other sections may be present, but these are not well standardized across man pages. Common examples
include: OPTIONS, EXIT STATUS, RETURN VALUE, ENVIRONMENT, BUGS, FILES, AUTHOR,
REPORTING BUGS, HISTORY and COPYRIGHT.

Authoring
Manual pages can be written either in the old man macros, the new doc macros, or a combination of both
(mandoc).[22] The man macro set provides minimal rich text functions, with directives for the title line,
section headers, (bold, small or italic) fonts, paragraphs and adding/reducing indentation.[23] The newer
mdoc language is more semantic in nature, and contains specialized macros for most standard sections such
as program name, synopsis, function names, and the name of the authors. This information can be used to
implement a semantic search for manuals by programs such as mandoc. Although it also includes directives
to directly control the styling, it is expected that the specialized macros will cover most of the use-cases.[21]
Both the mandoc and the groff projects consider mdoc the preferred format for new documents.[24]

Although man pages are, to troff, text laid out using 10-point Roman type, this distinction is usually moot
because man pages are viewed in the terminal (TTY) instead of laid out on paper. As a result, the "small
font" macro is seldom used.[25] On the other hand, bold and italic text is supported by the terminal via
ECMA-48, and groff's grotty does emit them as requested when it detects a supporting terminal. The BSD
mandoc however only supports bold and underlined (as a replacement for italics) text via the typewriter
backspace-then-overstrike sequence, which needs to be translated into ECMA-48 by less.[26][27]

Some tools have been used to convert documents in a less contrived format to manual pages. Examples
include GNU's help2man, which takes a --help output and some additional content to generate a manual

5 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

page.[28] The manual would be barely more useful than the said output, but for GNU programs this is not an
issue as texinfo is the main documentation system.[29] A number of tools, including pandoc, ronn, and
md2man support conversion from Markdown to manual pages. All these tools emit the man format, as
Markdown is not expressive enough to match the semantic content of mdoc. DocBook has an inbuilt man(7)
converter – of appalling quality, according to mandoc's author[30] who wrote a separate mdoc(7) converter.

Man pages are usually written in English, but translations into other languages may be available on the
system. The GNU man-db and the mandoc man is known to search for localized manual pages under
subdirectories.[31][16]:Overview[15]

Alternatives
Few alternatives to man have enjoyed much popularity, with the possible exception of GNU Project's "info"
system, an early and simple hypertext system. There is also a third-party effort known as TLDR pages
(tldr) that provides simple examples for common use cases, similar to a cheatsheet.[32]

In addition, some Unix GUI applications (particularly those built using the GNOME and KDE development
environments) now provide end-user documentation in HTML and include embedded HTML viewers such as
yelp for reading the help within the application. An HTML system in Emacs is also slated to replace
texinfo.[33]

See also
▪ List of Unix commands
▪ List of Plan 9 applications
▪ info
▪ apropos
▪ README
▪ RTFM
▪ ManOpen – NeXT/macOS graphical man utility

References
1. "man(1)" (https://man.freebsd.org/cgi/man.cgi?query=man&sektion=1). FreeBSD General Commands
Manual. Archived (https://web.archive.org/web/20230130060434/https://man.freebsd.org/cgi/man.cgi?q
uery=man&sektion=1) from the original on 2023-01-30. Retrieved 2023-07-15.
2. McIlroy, M. D. (1987). A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–
1986 (http://www.cs.dartmouth.edu/~doug/reader.pd�) (PDF) (Technical report). CSTR. Bell Labs. 139.
Archived (https://web.archive.org/web/20171111151817/http://www.cs.dartmouth.edu/~doug/reader.pd
�) (PDF) from the original on 2017-11-11. Retrieved 2015-02-01.

6 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

3. Darwin, Ian; Collyer, Geo�rey. "UNIX Evolution: 1975-1984 Part I - Diversity" (http://www.collyer.net/
who/geo�/history.html). Archived (https://web.archive.org/web/20120717002523/http://www.collyer.ne
t/who/geo�/history.html) from the original on 17 July 2012. Retrieved 22 December 2012. Originally
published in Microsystems 5(11), November 1984.
4. Fiedler, Ryan (October 1983). "The Unix Tutorial / Part 3: Unix in the Microcomputer Marketplace" (htt
ps://archive.org/stream/byte-magazine-1983-10/1983_10_BYTE_08-10_UNIX#page/n133/mode/2up).
BYTE. p. 132. Retrieved 30 January 2015.
5. "GIT commit 002a6339b1fe8f83f4808022a17e1aa379756d99" (https://git.savannah.nongnu.org/cgit/ma
n-db.git/commit/src/man.c?id=002a6339b1fe8f83f4808022a17e1aa379756d99). Archived (https://web.arc
hive.org/web/20171204003014/http://git.savannah.nongnu.org/cgit/man-db.git/commit/src/man.c?id=0
02a6339b1fe8f83f4808022a17e1aa379756d99) from the original on 4 December 2017. Retrieved
22 November 2017.
6. "GIT commit 84bde8d8a9a357bd372793d25746ac6b49480525" (https://git.savannah.gnu.org/cgit/man-d
b.git/commit/?id=84bde8d8a9a357bd372793d25746ac6b49480525). Archived (https://web.archive.org/w
eb/20180905095817/https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=84bde8d8a9a357bd37279
3d25746ac6b49480525) from the original on 5 September 2018. Retrieved 22 November 2017.
7. "GIT commit b225d9e76�bb0a6a4539c0992�ba88c83f0bd37e" (https://git.savannah.gnu.org/cgit/man-d
b.git/commit/?id=b225d9e76�bb0a6a4539c0992�ba88c83f0bd37e). Archived (https://web.archive.org/we
b/20201109034103/https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=b225d9e76�bb0a6a4539c0
992�ba88c83f0bd37e) from the original on 9 November 2020. Retrieved 25 September 2018.
8. " "Why does man print "gimme gimme gimme" at 00:30?" " (https://unix.stackexchange.com/question
s/405783/why-does-man-print-gimme-gimme-gimme-at-0030). Archived (https://web.archive.org/we
b/20171121230223/https://unix.stackexchange.com/questions/405783/why-does-man-print-gimme-gim
me-gimme-at-0030) from the original on 21 November 2017. Retrieved 22 November 2017.
9. Wright, Francis J. "WoMan: Browse Unix Manual Pages "W.O. (without) Man" " (https://www.gnu.org/
so�ware/emacs/manual/html_mono/woman.html). GNU. Archived (https://web.archive.org/web/20201
111204938/https://www.gnu.org/so�ware/emacs/manual/html_mono/woman.html) from the original
on 11 November 2020. Retrieved 3 August 2020.
10. Pali, Gabor, ed. (12 May 2013). "FreeBSD �uarterly Status Report, January-March 2013" (http://www.fr
eebsd.org/news/status/report-2013-01-2013-03.html#mdoc.su-%E2%80%94-Short-Manual-Page-URLs).
FreeBSD. Archived (https://web.archive.org/web/20141222022258/http://www.freebsd.org/news/status/
report-2013-01-2013-03.html#mdoc.su-%E2%80%94-Short-Manual-Page-URLs) from the original on 22
December 2014. Retrieved 25 December 2014.
11. Murenin, Constantine A. (19 February 2013). "announcing mdoc.su, short manual page URLs" (http://li
sts.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html). [email protected] (Mailing
list). Archived (https://web.archive.org/web/20140807051219/http://lists.freebsd.org/pipermail/freebsd-
doc/2013-February/021465.html) from the original on 7 August 2014. Retrieved 25 December 2014.
12. Murenin, Constantine A. (23 February 2013). "mdoc.su — Short manual page URLs for FreeBSD,
OpenBSD, NetBSD and DragonFly BSD" (http://mdoc.su/). Archived (https://web.archive.org/web/201
41217170726/http://mdoc.su/) from the original on 17 December 2014. Retrieved 25 December 2014.
13. "Linux man pages online" (http://man7.org/linux/man-pages/index.html). man7.org. Archived (https://
web.archive.org/web/20200507122101/http://www.man7.org/linux/man-pages/index.html) from the
original on 2020-05-07. Retrieved 2020-05-05.
14. "About" (https://www.mankier.com/about). ManKier. Archived (https://web.archive.org/web/202004251
12006/https://www.mankier.com/about) from the original on 2020-04-25. Retrieved 2020-05-05.
15. man(1) (https://www.freebsd.org/cgi/man.cgi?query=man&sektion=1) –
FreeBSD General Commands Manual
16. man(1) (https://www.mankier.com/1/man) – Linux General Commands Manual

7 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

17. "Manual Pages for Research Unix Eighth Edition" (http://man.cat-v.org/unix_8th/). man.cat-v.org.
Archived (https://web.archive.org/web/20200630215702/http://man.cat-v.org/unix_8th/) from the
original on 2020-06-30. Retrieved 2020-05-06.
18. "Unix Programmer's Manual - Introduction" (https://www.bell-labs.com/usr/dmr/www/manintro.html)
. www.bell-labs.com. November 3, 1971. Archived (https://web.archive.org/web/20200601064923/https://
www.bell-labs.com/usr/dmr/www/manintro.html) from the original on June 1, 2020. Retrieved May 6,
2020.
19. "System V release 4 manuals" (http://bitsavers.trailing-edge.com/pdf/att/unix/System_V_Release_4/).
bitsavers.trailing-edge.com. Archived (https://web.archive.org/web/20200803205815/http://bitsavers.trail
ing-edge.com/pdf/att/unix/System_V_Release_4/) from the original on 2020-08-03. Retrieved
2020-05-06.
20. "lapack (l) - Linux Man Pages" (https://www.systutorials.com/docs/linux/man/l-lapack/).
www.systutorials.com. Archived (https://web.archive.org/web/20230311130845/https://www.systutorial
s.com/docs/linux/man/l-lapack/) from the original on 2023-03-11. Retrieved 2021-05-29.
21. mdoc(7) (https://www.freebsd.org/cgi/man.cgi?query=mdoc&sektion=7) –
FreeBSD Miscellaneous Information Manual
22. groff_tmac(5) (https://www.mankier.com/5/groff_tmac) – Linux File Formats
Manual
23. man(7) (https://www.mankier.com/7/man) – Linux Miscellanea Manual
24. "Gro� Mission Statement - 2014" (https://www.gnu.org/so�ware/gro�/gro�-mission-statement.html).
www.gnu.org. Archived (https://web.archive.org/web/20201203121306/https://www.gnu.org/so�ware/gr
o�/gro�-mission-statement.html) from the original on 2020-12-03. Retrieved 2021-01-02. "Concurrent
with work on man(7), mdoc(7) will be actively supported and its use promoted."
25. "man" (https://www.gnu.org/so�ware/gro�/manual/html_node/man.html). The GNU Tro� Manual.
Archived (https://web.archive.org/web/20191224124039/https://www.gnu.org/so�ware/gro�/manual/ht
ml_node/man.html) from the original on 24 December 2019. Retrieved 31 December 2019.
26. "Italics and colour in manual pages on a nosh user-space virtual terminal" (https://jdebp.uk/So�wares/
nosh/italics-in-manuals.html). jdebp.eu. Archived (https://web.archive.org/web/20210128033617/http
s://jdebp.uk/So�wares/nosh/italics-in-manuals.html) from the original on 2021-01-28. Retrieved
2021-01-21.
27. mandoc(1) (https://www.freebsd.org/cgi/man.cgi?query=mandoc&sektion=1)
– FreeBSD General Commands Manual. "Font styles are applied by using back-spaced encoding..."
28. "help2man Reference Manual" (https://www.gnu.org/so�ware/help2man). Archived (https://web.archi
ve.org/web/20230306093151/https://www.gnu.org/so�ware/help2man/) from the original on 6 March
2023. Retrieved 5 March 2023.
29. "Man Pages (GNU Coding Standards)" (https://www.gnu.org/prep/standards/html_node/Man-Pages.h
tml). www.gnu.org. Archived (https://web.archive.org/web/20230305170922/https://www.gnu.org/prep/s
tandards/html_node/Man-Pages.html) from the original on 2023-03-05. Retrieved 2023-03-05.
30. Ingo Schwarze. "New mandoc -mdoc -T markdown converter" (https://undeadly.org/cgi?action=article
&sid=20170304230520). undeadly.org. Archived (https://web.archive.org/web/20230305170920/https://u
ndeadly.org/cgi?action=article&sid=20170304230520) from the original on 2023-03-05. Retrieved
2023-03-05. – for speci�ic complaints by the author, see Ingo Schwarze (28 February 2014). "Re: Gro�
man pages (tangential to Future Redux)" (https://lists.gnu.org/archive/html/gro�/2014-02/msg00109.ht
ml). Gro� (Mailing list). Archived (https://web.archive.org/web/20230305171936/https://lists.gnu.org/ar
chive/html/gro�/2014-02/msg00109.html) from the original on 2023-03-05.
31. "command line - Linux man pages in di�erent languages" (https://askubuntu.com/a/1113662). Ask
Ubuntu. Archived (https://web.archive.org/web/20230311130846/https://askubuntu.com/questions/1113
648/linux-man-pages-in-di�erent-languages/1113662) from the original on 2023-03-11. Retrieved
2020-05-05.

8 of 9 3/19/25, 6:11 PM
man page - Wikipedia https://en.wikipedia.org/wiki/Man_page

32. "TLDR pages" (https://tldr.sh/). tldr.sh. Archived (https://web.archive.org/web/20200427081953/https://t

ldr.sh/) from the original on 2020-04-27. Retrieved 2020-05-05.
33. Raymond, Eric S. "Re: [Gro�] man pages (tangential to Future Redux)" (https://lists.gnu.org/archive/ht
ml/gro�/2014-02/msg00104.html). gro� (Mailing list). Archived (https://web.archive.org/web/202303051
71106/https://lists.gnu.org/archive/html/gro�/2014-02/msg00104.html) from the original on 2023-03-05.
Retrieved 2023-03-05 – via lists.gnu.org.

External links
▪ History of UNIX Manpages (https://manpages.bsd.lv/history.html) for a primary-source history of
UNIX man pages.
▪ UNIX and Linux Man Page Repository (https://www.unix.com/man-page-repository.php) with nearly
300,000 well formatted man pages.
▪ What do the numbers in a man page mean? (https://unix.stackexchange.com/questions/3586/what-do-
the-numbers-in-a-man-page-mean)
▪ FreeBSD Manual Pages (https://www.freebsd.org/cgi/man.cgi), freebsd.org – has also man pages for
Darwin, Debian, HP-UX, IRIS, NetBSD, OpenBSD, NextSTEP, SunOS and more

Retrieved from "https://en.wikipedia.org/w/index.php?title=Man_page&oldid=1278377223"

9 of 9 3/19/25, 6:11 PM