.1

1 File

Unix Manual Page (section 1 - user commands)
Ask a question
QUICK ANSWER

A .1 file is a Unix manual page - the reference documentation for a user command, written in roff/troff markup. On Linux or macOS, read it by running "man ./name.1" in a terminal; groff formats it to text, HTML, or PDF. The file is plain text and safe to open in any text editor, though you will see raw markup rather than the formatted page.

Developer: Bell Labs (Unix man system); groff maintained by the GNU Project Category: Misc Files Open standard MIME: text/troff
OPENS ON Windows macOS Linux
Related: .TORRENT · .MSO · .MD5 · .SHS

On this page

19k+ extensions indexed
Last reviewed Sep 6, 2026

Not sure what your file is?

Drop any file into our identifier - we read just the first bytes to name the format.

Identify a file

What is the 1 file format?

.1 files store Unix manual pages in plain-text format, specifically for section 1 - executable programs and user commands. They are commonly referred to as man pages and are written in .roff markup using the man macro package (groff), with dot-prefixed directives such as .TH, .SH, .B, and .TP controlling layout when rendered.

Man pages are viewed by running man name_of_the_application in a Unix terminal. The numeral suffix indicates the manual section: .1 covers user commands, while .2 through .8 cover system calls, library functions, file formats, games, and administration commands respectively. All sections share the same underlying roff source format.

Man page files may be stored compressed - on most Linux and macOS systems they live at paths such as /usr/share/man/man1/ls.1.gz and are decompressed on demand by the man command. The .gz compression is invisible from the user's perspective.

Windows uses a different help system: in graphical mode, help is accessed by pressing F1, and from PowerShell by appending /? or -? to a command. For Unix-style man pages on Windows, the Windows Subsystem for Linux (WSL) provides a full man and groff environment. Of course, man page files must be installed for a given application before they can be displayed on any platform.

Security & safety

RISK: LOW

A man-page source is plain text and does not execute on viewing. The only theoretical caution is that roff is a Turing-complete macro language and groff has historically had parsing bugs, so rendering a .1 from a wholly untrusted source is best done with the safer, sandboxed mandoc rather than full groff. In normal use (reading docs from packages and projects) a .1 file is harmless; opening it in a text editor is completely safe.

Format details

in a nutshell
FULL NAMEUnix Manual Page (section 1 - user commands)aka man page, troff/groff man-macro source
DEVELOPERBell Labs (Unix man system); groff maintained by the GNU Projectsince 1971 (Unix Programmer's Manual, V1); man macros standardized over the 1970s-80s
CATEGORYMisc Files
MIME TYPEtext/troff
TYPEPlain-text troff/groff source using the man macro package (roff markup)
STANDARDOpen · royalty-free

Programs that open 1 files

Windows2 apps
WSL (man + groff) Built-in In Windows Subsystem for Linux run 'man ./name.1'; or install groff via MSYS2 to render the page.
Notepad / any text editor Free Open the .1 source as plain text to read the raw roff markup on Windows (no formatting applied).
macOS2 apps
man / groff (built-in) Built-in macOS ships man and groff: 'man ./name.1' to read it; groff to convert to text/PS/PDF.
Terminal text editor / BBEdit Freemium Open the .1 source in any editor to view/edit the roff markup.
Linux3 apps
man (man-db) Open-source Run 'man ./name.1' to view it formatted in the terminal; man calls groff to render bold/italics.
groff Open-source Render directly: 'groff -man -Tascii name.1 | less' for text, '-Thtml' for HTML, '-Tpdf' for PDF.
Text editor (Vi/Vim, GNU Emacs, nano, Notepad++) Open-source Open the raw .1 source to read/edit the roff markup (you'll see .TH, .SH macros, not a formatted page).

Technical details

deep spec
Format typePlain-text roff/groff source using the man macro package
EncodingASCII or UTF-8 plain text; no binary header or BOM required
MIME typetext/troff (also accepted as application/x-troff-man)
File signatureNo binary magic bytes; man sources conventionally begin with a .TH title line, e.g. .TH LS 1
Manual section coveredSection 1 - executable programs and general user commands
Markup macros.TH (title/header), .SH (section heading), .B (bold), .I (italic), .TP (tagged paragraph), .PP (paragraph break)
On-disk storageFrequently gzip-compressed as name.1.gz, stored under /usr/share/man/man1/ on Linux
Typical uncompressed size1 KB - 100 KB
Renderer / viewerProcessed by groff or nroff; displayed via the man command in a terminal
Standard page structureMandatory sections: NAME, SYNOPSIS, DESCRIPTION; common additions: OPTIONS, FILES, SEE ALSO, AUTHOR, BUGS
Sibling section extensions.2 (system calls), .3 (library functions), .5 (file formats), .8 (system administration)
Associated operating systemsLinux, macOS, BSD variants; available on Windows via WSL (Windows Subsystem for Linux)
Developer / maintainerOriginated at Bell Labs (1971); groff implementation maintained by the GNU Project
Pre-formatted variantSome .1 files are cat pages - pre-rendered text with backspace-overstrike bold, not roff source
Released1971 (Unix Programmer's Manual, V1); man macros standardized over the 1970s-80s
Latest versionN/A (roff/man-macro convention; groff is the active implementation)
Open standardYes · royalty-free
Specificationman7.org

1 conversions

Community Q&A

asked by users
Ask a quick question
Get help from people who work with 1 files. Be specific - include your system and software version.
No account needed · answers usually within a day

No questions yet - be the first to ask about 1 files.

Frequently asked questions

What is a .1 file?
A Unix manual page ('man page') in section 1 (user commands) - plain-text documentation written in roff/troff with the man macros. The '1' is the manual section number, not a file type.
How do I read a .1 man page file?
On Linux/macOS/BSD run 'man ./name.1' to view it formatted in the terminal. To render it elsewhere, 'groff -man -Tascii name.1 | less'. A text editor shows the raw markup.
How do I convert a man page to PDF?
Use groff: 'groff -man -Tpdf name.1 > name.pdf'. For HTML use 'groff -Thtml' or 'mandoc -T html'.
Why does my .1 file show .TH and .SH instead of normal text?
Because you're seeing the raw roff source. Those dot-macros are formatting instructions; run the file through 'man' or 'groff' to render the finished page.
What do the man section numbers (1, 2, 3, 5, 8) mean?
1 = user commands, 2 = system calls, 3 = library functions, 4 = devices, 5 = file formats, 6 = games, 7 = conventions, 8 = admin commands. The file's numeric extension is its section.
Is every file ending in 1 a man page?
No. The numeral '1' is also a generic counter - e.g. a log-rotation backup (syslog.1) or a numbered split part. It's a man page only if the contents are roff/man-macro text.

References

1GNU groff - manual page formatterwww.gnu.org
2man7.org - man(7): macros to format manual pagesman7.org

Keep exploring

across the database

Top extensions this week

1.AQQAQQ Instant Messenger File
2.CRDOWNLOADChrome Partial Download File
3.PARTPartial Download File
4.MDMarkdown Document
5.JPGJPEG Image
6.EXEWindows Executable (Portable Executable)
7.BINCD/DVD Disc Image (BIN/CUE)
8.NOMEDIAAndroid No-Media Marker File
9.DATProgram Data File (generic)
10.RPMSGRestricted Permission Message

Related extensions

.TORRENTBitTorrent Metainfo File
.MSOMicrosoft Office HTML/OLE Data Stream (oledata.mso)
.MD5MD5 Checksum File
.SHSShell Scrap Object File
.DDDAdobe Acrobat Distiller file
.DWLDrawing Lock File (CAD)

Free file tools

An in-browser file identifier and image converter - everything runs on your device.

Open the toolbox

Browse file extensions A-Z