Word processor

On this page 8

A word processor is an application for creating, editing, formatting and printing text documents, from one-page letters to book-length reports. Among office applications it is the core tool for structured written content, and in software terms it combines a text editor, a layout and pagination engine and a document file format that stores both the words and their presentation.

Unlike a plain text editor, a word processor understands paragraphs, styles, pages, sections, tables, images and references. It reflows text automatically as content changes, which is why the category replaced typewriters and dedicated word processing machines during the 1980s and remains one of the most widely used kinds of desktop and web software.

How a word processor represents a document

A word processor stores a document as a tree of structured objects, not as a stream of characters. The body contains paragraphs, each paragraph contains runs of text with uniform formatting, and higher containers such as sections, headers, footers, tables and text boxes hold their own content.

Formatting is resolved through a cascade of properties. Direct formatting applied to a run overrides the character style, which overrides the paragraph style, which in turn inherits from the document defaults. This layered model explains why a document can look correct while behaving unpredictably: direct formatting hides the style structure that later edits depend on.

The layout engine turns this logical structure into pages. It measures glyphs using font metrics, breaks lines with hyphenation and justification rules, applies widow and orphan control, places floating objects and recalculates fields such as page numbers. Because every edit can change line breaks on later pages, layout runs continuously in the background.

The table below summarizes the main layers of the document model and what each one controls.

LayerWhat it controlsTypical examples
Document defaultsBase font, language, paper size11 pt body font, A4 or US Letter
SectionPage geometry and headersMargins, orientation, columns
Paragraph styleBlock-level appearanceHeading 1, Body Text, Quote
Character styleInline appearanceEmphasis, code, citation
Direct formattingOne-off overridesManually bolded word, changed color
FieldsComputed contentPage number, date, cross-reference
Layers of the word processor document model

Core features of word processing software

Modern word processors share a common feature set that goes well beyond typing. The most valuable features are those that keep long documents consistent and allow several people to work on the same text.

  • Styles and templates define the look of headings, body text and lists once and apply it everywhere.
  • Automatic numbering handles headings, lists, figures, tables and footnotes.
  • Generated content builds tables of contents, indexes and bibliographies from the document structure.
  • Track changes and comments record who changed what, so edits can be reviewed, accepted or rejected.
  • Mail merge combines a template with a data source to produce personalized letters or labels.
  • Proofing tools check spelling, grammar and readability for each language set on the text.
  • Version history and co-authoring let several editors work at once in cloud-based products.

These features rely on the document model described above. A table of contents, for example, works only when headings use real heading styles; text that merely looks like a heading because it is large and bold is invisible to the generator.

File formats used by word processors

The file format determines how faithfully a document survives exchange between programs. Current mainstream formats are zipped XML packages, while older binary formats and simpler interchange formats remain in circulation for compatibility and archiving.

The following table compares the formats a word processor most commonly reads and writes.

FormatStructureStandardBest use
DOCXZIP package of XML partsECMA-376, ISO/IEC 29500Default exchange in business
ODTZIP package of XML partsODF, ISO/IEC 26300Open standard, public sector
DOCBinary compound fileProprietary, later documentedLegacy documents only
RTFPlain text with control wordsProprietary specificationSimple cross-program exchange
PDFFixed page descriptionISO 32000Final distribution, not editing
MarkdownPlain text with light markupInformal, CommonMarkTechnical writing, version control
Common document formats and their roles

Conversion between formats is never perfectly lossless. Features with no equivalent in the target format, such as specific field codes, content controls or advanced text effects, are approximated or dropped, and differences in font availability alter line and page breaks.

A word processor occupies the middle ground between text editors and page layout software. Choosing the right tool depends on whether the priority is structure, visual precision or collaboration.

Tool categoryPrimary focusStrengthTypical limitation
Plain text editorRaw charactersSpeed, no hidden formattingNo pages or styles
Word processorStructured flowing textStyles, review, referencesLimited precise layout
Desktop publishingPage designExact typography and placementWeak editing workflow
Typesetting systemMarkup compiled to pagesMathematics, consistencySteep learning curve
Online document editorReal-time collaborationSimultaneous editing, sharingFewer advanced features
Word processor and neighboring tool categories

Within an office suite, the word processor sits beside the spreadsheet and the presentation program. Data and charts are often embedded or linked from a spreadsheet, which keeps figures in one authoritative place instead of retyping them.

Working effectively with a word processor

Productive use of a word processor depends on style-based authoring: decide the structure first, apply styles consistently and let the program handle numbering and layout. Organizations usually encode this discipline in templates that carry approved styles, page setup and boilerplate.

The decision table below matches common situations with a recommended approach.

SituationRecommended approachReason
Long report with chaptersHeading styles and generated contentsNumbering and navigation stay accurate
Contract under negotiationTrack changes with named reviewersEvery edit remains auditable
Hundreds of personalized lettersMail merge from a data sourceOne template, no manual copying
Document for external archiveExport to PDF/A after final reviewFixed appearance over time
Cross-platform team editingShared cloud document or DOCXWidest compatibility
Choosing an approach for typical documents

Limitations and common mistakes

Most problems with word processor documents come from manual formatting that imitates structure. Spaces or repeated tabs used for alignment, empty paragraphs used for spacing and manual page breaks used to start chapters all break as soon as text changes.

  • Missing fonts on another computer change metrics and move page breaks.
  • Unaccepted tracked changes and hidden comments can leak confidential drafting history.
  • Embedded metadata such as author names and template paths travels with the file.
  • Very large documents with many images slow layout; linking or splitting helps.
  • Accessibility suffers when headings are not styled and images lack alternative text.

Before distribution, a careful author runs the document inspector or equivalent tool, accepts or rejects all changes and checks the accessibility report, because these steps prevent the most frequent and most embarrassing failures.

The simple explanation

A word processor is a program for writing documents on a computer. You type the text, and the program takes care of how it looks on the page: margins, fonts, page numbers and where each page ends.

The big advantage over a typewriter is that nothing is fixed until you print or send it. You can move a paragraph, fix a typo or change every heading at once, and the program rearranges the pages for you. Think of it as a smart sheet of paper that tidies itself every time you change something.

How it is used in practice

A regional hospital prepares an annual quality report of about 80 pages written by six department heads. The communications team creates a template with heading styles, a numbered caption style for figures and a cover page, then shares it as a single cloud document so each author writes in an assigned chapter.

Authors work with track changes enabled, and the quality manager reviews every edit before accepting it. Charts are linked from the department spreadsheets, so late corrections to the figures update automatically. When the text is final, the team regenerates the table of contents, runs the accessibility checker, removes comments and exports an accessible PDF for publication. The result is a consistent report produced in three weeks instead of the six weeks the earlier, email-based process required.