Pular para o conteúdo principal
🇬🇧 English 🇪🇸 Español 🇩🇪 Deutsch
Conversor de imagens Conversor de vídeo Conversor de áudio Conversor de documentos
Ferramentas Guias Formatos Preços API
Entrar
MAN file
man
Formato de arquivo

Sobre os arquivos MAN

Unix Man Page

Lançado em 1971 Por Bell Labs (Unix V1)

Formato troff/groff para manuais Unix (desde 1971). Sintaxe densa com macros. Padrão para documentação de comandos shell e bibliotecas C.

Família

Documents & Text

Extensão

.man

Tipo MIME

text/troff

Pode ser usado como

Entrada Saída
A história

COMO NASCEU O
FORMATO MAN.

Unix man pages date to 1971, when Unix First Edition shipped at Bell Labs. Ken Thompson and Dennis Ritchie needed a way to document system calls, commands, and library functions, so they wrote short pages in `roff` (an early typesetting language) that could be formatted for either the teletype or a phototypesetter. The `man` command displayed these pages interactively in a pager. Fifty-plus years later every Unix-like OS still uses man pages as its primary command-line documentation.

A .man file (also called .1, .2, ..., .8 depending on the man section) is typically written in `troff` with either the `mdoc` or `man` macro package. The FreeBSD documentation, OpenBSD, Linux coreutils, and every Unix toolchain author ship man pages as their canonical docs. Running `man ls` on any Unix system renders one of these ancient files into your terminal — a toolchain older than the C language, TCP/IP, or the personal computer itself.

CURIOSIDADES E
FATOS INTERESSANTES.

01

Unix man pages date to 1971 — older than C, TCP/IP, email, and most things you consider "the internet".

02

Man pages are organized into 8 numbered sections — 1 for commands, 2 for system calls, 3 for library functions, and so on.

03

The classic "RTFM" ("read the fine manual") joke specifically refers to reading Unix man pages.

04

Modern tools (tldr, cheat, bro pages) exist because man pages are notoriously terse — but those tools complement, not replace, man.

05

The `roff` typesetting language that powers man pages predates TeX by 7 years and is still maintained in 2026.

VANTAGENS E
LIMITAÇÕES.

Vantagens

  • Universal Unix-like OS documentation since 1971.
  • Plain text with simple troff markup — tiny files.
  • Section system cleanly separates commands from APIs from config files.
  • Renders to terminal, PostScript, HTML, or PDF.
  • Every Unix programmer knows the format.

Limitações

  • Terse by design — bad for tutorials or beginner-friendly intros.
  • Troff syntax is arcane and difficult for modern authors.
  • No interactive examples or live-editable snippets.
  • Mostly replaced by web docs, cheat sheets, and --help output for modern tools.

Tamanhos típicos de arquivo

Single command man page

2-15 KB

Complex tool (e.g., bash man)

80-200 KB

Especificações técnicas

MIME type
text/troff
Extensions
.man, .1, .2, .3, .4, .5, .6, .7, .8
Markup
troff / groff with mdoc or man macro package
Renderer
groff + less (terminal), groff → PostScript/PDF/HTML
First shipped
Unix First Edition (1971)

CONVERTER A PARTIR DE
MAN

Casos de uso comuns

Unix/Linux documentation, command-line tool references, system administration

Formatos relacionados

Comparativos populares

Conversões populares de MAN

Os destinos mais procurados ao converter arquivos MAN.

Perguntas frequentes sobre MAN

Perguntas frequentes

MAN (Unix Man Page) is a document formato used to store paginated text, com optional formatoting, tables, images, hyperlinks, headers e footers. It sits no documents & text family e is tipicamente associated com a specific office suite ou publishing pipeline that defined the formato e ships the canonical reader.

Modern office suites — Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages — abrir most MAN arquivos com reasonable fidelity. If your installed software does not support MAN, converter to DOCX ou PDF first usando KaijuConverter; both abrir in virtually every reader, including grátis online viewers.

Upload the MAN to KaijuConverter e pick DOCX, PDF, ODT, RTF, HTML, Markdown, ou plain text. Our pipeline runs LibreOffice headlessly plus pandoc para text formatoos — the same engines behind profissional document pipelines. Styles, tables, images, e hyperlinks survive the conversion intact.

Sim, para um alta degree. padrão fonts, headings, lists, tables, images, hyperlinks e page structure transfer cleanly. Custom fonts substitute para o closest match if not embedded; obscure layout features unique to MAN (frames, legacy macros) may flatten to static content no target formato.

Usamos cookies e tecnologias similares para personalizar conteúdo e anúncios, e para analisar o tráfego. Mais informações sobre cookies.