You're reviewing a contract, pleading, or website that displays § and ¶, and the two marks look close enough to treat as interchangeable. They aren't. A misplaced symbol can send a reader to the wrong citation unit, while the font used to render that symbol can raise a separate licensing question if it's being served from a live website.
That combination makes paragraph symbol law more than a punctuation topic. It sits at the intersection of legal structure, document accessibility, search and extraction, typography, and compliance. This guide explains the distinction in plain language, then follows the mark through citation workflows and font audits. The discussion is informational and isn't legal advice.
Why the Paragraph Symbol Matters in Legal Writing
A junior associate is finalising a long contract appendix. Her keyboard macro inserts the pilcrow quickly, so the references begin appearing as ¶ 4.2 instead of § 4.2. The document still looks polished, but the symbols now point readers toward different structural units. Opposing counsel notices the inconsistency during review, and the drafting team has to check every reference before circulation.
That problem isn't cosmetic. The section sign, §, identifies numbered or lettered statutory sections and similar structural provisions. The pilcrow, ¶, identifies a paragraph, particularly a sequentially numbered paragraph in a complaint, declaration, brief, or other prose-based legal document. Guidance for legal typography makes this distinction explicit: the paragraph mark is used for numbered paragraphs, while the section mark is reserved for statutory sections and comparable units. See the legal typography guidance on paragraph and section marks.
One visual resemblance, two meanings
A citation such as § 4.2(a) tells the reader to look for a section and its subsection. A citation such as ¶ 12 tells the reader to locate a numbered paragraph. If a document uses the wrong mark, a human reviewer may still infer the intended reference, but a citation checker, document parser, or automated cross-reference system may not.
The symbol's history also explains why it has staying power. The pilcrow developed from older manuscript marking systems. The Greek paragraphos appeared in the 4th century AD, a medieval form using C for capitulum evolved toward the familiar mark, and the modern form has been used since the 15th century. In legal writing, the mark became a practical way to point to exact paragraphs before indentation and spacing conventions became reliable. These historical details are documented in the reference material on the section sign and pilcrow.
Practical rule: Identify the citation unit first, then choose the symbol. Don't choose the mark because it's faster to type.
The same discipline helps teams that use automated drafting or editing systems. If you're building a repeatable legal-content workflow, it can help to find the right AI outline tool before drafting, but the outline won't resolve symbol ambiguity by itself. Human review still has to confirm whether each reference points to a section, subsection, paragraph, or another unit. Font compliance deserves the same attention, especially where legal teams publish client-facing documents and websites. A related discussion of why law firms can't ignore font licensing compliance is useful context for that review.
Anatomy of the Section Sign and Pilcrow
The quickest way to understand these characters is to separate character identity from glyph appearance. A character is the encoded text value stored in a document. A glyph is the visual shape supplied by a typeface. Developers, designers, and legal reviewers need to check both.
The section sign § is Unicode U+00A7, and the pilcrow ¶ is Unicode U+00B6. Both sit in the Latin-1 Supplement block. Typing the character directly is preferable to using a text substitute, because a real Unicode character gives software a consistent value to copy, search, extract, and interpret.
Common input methods
On Windows, users can enter the section sign with Alt+0167 and the pilcrow with Alt+0182, using the numeric keypad. On macOS, Option+6 produces § and Option+7 produces ¶. In many GTK environments on Linux, Ctrl+Shift+U, followed by 00A7 or 00B6, then Enter, inserts the corresponding character.
Keyboard shortcuts vary by application and layout, so teams should test the method used in their actual authoring environment. Mobile users may find the characters in a symbol menu or create a text replacement, but a replacement should insert the correct character rather than a visual imitation.
The shape still matters
Two files can contain U+00A7 and look noticeably different. One typeface may draw the section sign with an open upper loop, while another closes it. Pilcrow shapes can also vary with typeface design and script tradition. A reader may recognise both as the same character, yet differences in stroke weight, spacing, and proportions can affect legibility in dense legal text.
| Attribute | Section Sign (§) | Pilcrow (¶) |
|---|---|---|
| Unicode value | U+00A7 | U+00B6 |
| Primary legal reference | Numbered statutory or structural section | Numbered paragraph |
| Windows input | Alt+0167 | Alt+0182 |
| macOS input | Option+6 | Option+7 |
| Main audit question | Does the intended font contain and render the character? | Does the intended font contain and render the character? |
The same code point can render differently in Times New Roman, Helvetica, Arial, or another family. That matters during font auditing because the visible mark can reveal which typeface a browser or document is using, while the underlying text still reports only U+00A7 or U+00B6.
Section Mark Versus Pilcrow in Legal Citation
Legal citation becomes clearer when you ask a simple question: What does the number describe? If it identifies a statutory section, use §. If it identifies a numbered paragraph in a document, use ¶.
A statutory reference might appear as § 1983, while multiple statutory sections might appear as §§ 1983–1988. Paragraph references use the corresponding single and plural forms, ¶ 12 and ¶¶ 12–14. Bluebook-based guidance also addresses spacing, plural symbols, and the placement of the word “at.” It directs writers to place a space after the symbol before the number, use doubled symbols for plural references, and avoid preceding the paragraph symbol with “at.” See the Bluebook-based citation guidance.
Compare the citation units
| Citation Element | Section Sign (§) | Pilcrow (¶) |
|---|---|---|
| Single reference | § 1983 | ¶ 12 |
| Multiple reference | §§ 1983–1988 | ¶¶ 12–14 |
| Typical source | Statute, regulation, structured clause | Complaint, declaration, brief, witness statement |
| Meaning of the number | Section or provision | Numbered paragraph |
| Main risk | Reader follows the wrong statutory unit | Reader searches for a paragraph that isn't intended |
A contract clause labelled § 4.2(a) suggests a section-and-subsection hierarchy. The same visible content labelled ¶ 4.2(a) suggests a paragraph within a numbered sequence. That distinction gives the symbol a structural role. It tells the reader how the source is organised before the reader even opens the cited provision.
Why automated systems care
Legal repositories and internal review systems often extract citations from text. A parser that treats § and ¶ as interchangeable may create broken links, inaccurate indexes, or misleading review results. A human can often repair an obvious typo from context, but downstream software needs stable signals.
The formatting itself should be tested. Confirm the character, the space after it, the number range, and the use of doubled symbols. For designers working on formal documents, a guide to font choices for legal documents can help frame the typography review, but font selection doesn't replace citation proofreading.
How Legal Texts Use These Symbols
A citation's meaning depends on the document around it. In a statute, the section sign points to the statute's numbered structure. In a contract, it can identify a clause or subsection. In a legal brief, it may direct the reader to an external statutory provision, while the pilcrow usually points to a numbered paragraph within the brief.
The symbol also gives an audit reviewer a useful trail. A page containing § 230(c)(1) signals a statutory citation to verify. A contract containing § 4.2(a) signals an internal clause structure. Those marks can help locate documents, templates, and font deployments that deserve review, especially when the same legal material appears in PDFs, word-processing files, and web pages.
A single provision uses one section sign, such as § 230(c)(1). Multiple provisions use the doubled form, such as §§ 12–18 for a range or §§ 12, 14 for separate sections. Numbered paragraphs follow the same singular and plural pattern with ¶ and ¶¶.
The surrounding style changes the result
Citation conventions vary by jurisdiction and document type. Some systems use abbreviations such as reg. for regulation or art. for article. A team working across jurisdictions should follow the governing manual or house style rather than carrying a familiar U.S. convention into every document.
| System | Document | Example | Plural | Spacing |
|---|---|---|---|---|
| U.S. legal citation | Statute | § 230(c)(1) | §§ 12–18 | Follow the applicable citation guide |
| U.S. legal drafting | Numbered pleading paragraph | ¶ 12 | ¶¶ 12–14 | Place the number after the symbol |
| Contract drafting | Internal clause | § 4.2(a) | House-style dependent | Apply the contract's defined structure |
| Cross-jurisdictional practice | Regulation or treaty text | reg. or art. reference | Manual-dependent | Verify the governing style |
Subsection order must remain exact. § 230(c)(1) and § 230(1)(c) are different strings, and a reader or parser may be directed to a different provision by the change.
Footnotes and internal references
Editorial systems may place reference marks in sequences that include asterisks, daggers, double daggers, and pilcrows. The pilcrow can also mark a paragraph break in quoted material or identify a precise paragraph in a legal document. Its role therefore extends beyond courtroom citation.
Consistent symbols help indexing systems connect citations, update references, and identify broken destinations. They also give reviewers a comparison point when PDF conversion, scanning, or OCR changes spacing or replaces a character. During a font audit, verify that the deployed typeface contains the intended section and paragraph glyphs, then compare the rendered output with extracted text. A correct-looking citation can still expose an unverified font file or deployment path, so citation review and licensing review should record the same document location.
Desktop Versus Web Font Licensing Explained
A section sign can look correct while pointing to the wrong deployment. A desktop font licence generally covers local installation on an authorised computer for design and production work. A web font licence covers delivery to site visitors through a browser. The permissions are separate, as this desktop versus web font licensing overview explains. For a detailed comparison of the categories, see our guide to the licensing differences between web and desktop fonts.
Follow the file, not just the design
A desktop-licensed TTF or OTF may support a local layout, printed document, or static PDF workflow. Uploading that file to a live site is a separate deployment. The same applies after conversion to WOFF2. Webfonts travel from a server to a browser and are commonly declared with CSS @font-face; formats can include WOFF, WOFF2, and EOT. This webfont mechanics guidance explains why browser delivery needs its own licensing review.
The section sign is a useful audit glyph because professional typefaces commonly contain it. Its appearance does not establish compliance. During an audit, trace the glyph from the rendered citation to the font file, stylesheet, server, and documented permission. Record the document location so a reviewer can compare the visible character with the deployed asset.
Licences may set different limits. Web rights can use pageview tiers or an annual fee, while desktop rights are often tied to authorised users or devices. Some web licences allow several controlled websites but still impose a pageview limit. Agencies should document domains, deployments, and authorised machines. Teams reviewing formatting standards can consult court-approved font choices, then confirm the actual licence terms for every file.
Where Typography Meets Licensing Risk
Many font reviews stop when the page looks correct. That's where avoidable problems can remain hidden. A browser may use one font for live text, a fallback for a missing glyph, and another face during printing or export. The visible section sign can therefore be a useful diagnostic clue, but it isn't proof that the entire type stack is compliant.
Failure modes that deserve inspection
- Fallback chains: A licensed desktop family may be replaced by an unlicensed webfont when a browser, print engine, or export workflow encounters a missing glyph.
- Trial files: A demo or trial font may enter a production bundle through marketing collateral, a template, or a contractor handoff.
- Untracked uploads: A contractor may self-host a font file without preserving the purchase record, licence scope, or deployment approval.
- Persistent caches: A content delivery cache may continue serving a font after the relevant rights lapse or the deployment changes.
- Document embedding: A font embedded in a PDF or other shared file may travel beyond the use permitted by its licence.
The risk isn't the symbol. It's the file path the symbol travels through, from a designer's workstation to a build system, server, browser, export tool, or shared document.
Build a defensible record
A useful audit trail connects the deployed asset to its permission. Keep the licence PDF, purchase or authorisation record, font filename, family and version, deployment timestamp, source repository, and destination server or content delivery location. Record which domains and machines are covered, and preserve remediation evidence when a file is removed or replaced.
The legal exposure can be significant. A legal summary notes that unlicensed use, installation beyond permitted workstations, or use in an excluded context can support infringement claims, and that willful infringement under U.S. copyright law can carry statutory damages of up to $150,000 per infringed work under 17 U.S.C. § 504(c). See the legal summary of typeface and font copyright exposure. This is informational compliance guidance, not legal advice.
For a broader operational framework, teams can review legal risk mitigation for fonts and web typography.
Accessibility, Indexing, and Verifying Your Typography
Treat § as semantic content, not decoration. Assistive technology may announce it as “section” or “section sign,” depending on the reader and language. If a citation remains understandable when the symbol is ignored or spoken differently, the document is more resilient.
A practical approach is to pair the symbol with meaningful text where the context is unfamiliar. For example, accessible text can identify section 230 rather than relying on the reader to interpret a symbol. Preserve reading order in headings, tables, footnotes, and tagged PDFs, and avoid image-only legal citations.
Search and extraction need redundancy
Search engines can index Unicode characters, but relying on the glyph alone is fragile. Copying, font fallback, OCR, localisation, normalisation, and lost PDF text layers can change what a system receives. Keep matching textual metadata, descriptive URLs, and visible text in the document source. Don't place a legal citation only inside an image.
Verification should cover the environments readers use:
- Check the character: Confirm that the source contains U+00A7 for § or U+00B6 for ¶.
- Check presentation: Review spacing, wrapping, line breaks, glyph shape, and fallback behaviour.
- Check extraction: Compare visible PDF text with copied and extracted text.
- Check assistive output: Test screen-reader announcements and reading order.
- Record evidence: Preserve the font family, version, character support, licence scope, test environment, and remediation result.
A live-page, PDF, image, and font-set review can be organised through a website font checker and complete audit guide. The principle remains tool-independent: verify the character, the rendering path, and the rights attached to the file.
Frequently Asked Questions About the Paragraph Symbol
What does the section sign mean?
The section sign § means “section” and normally appears before a provision number. In standard U.S. citation style, a reference is commonly written as § 1983, with a space between the symbol and number under Bluebook-based operational guidance. House style, jurisdiction, and national conventions can differ, so the controlling manual should decide.
For multiple provisions, use §§. A range can appear as §§ 12–18, while separate provisions can appear as §§ 12, 14. The doubled mark tells the reader that more than one section follows.
Is the pilcrow the same as the section sign?
No. The pilcrow, ¶, marks a paragraph and commonly appears in numbered paragraphs in pleadings, declarations, briefs, and related documents. It's less common as the primary symbol in formal statutory citation. A pilcrow reference such as ¶ 12 points to a paragraph, not a statutory section.
The characters also have different Unicode values. The section sign is U+00A7, while the pilcrow is U+00B6. They shouldn't be substituted for each other merely because both are familiar legal and editorial marks.
How do you type §?
On Windows, use Alt+0167 with the numeric keypad. On macOS, use Option+6. Many mobile keyboards place § in a symbol menu, and text-replacement settings can insert it when a shortcut is entered.
Use the actual Unicode character rather than a text substitute. Copy-paste confirms the character value, but it doesn't reveal which font owns the visible glyph. That requires checking the document or page's font stack and the file used to render it.
Can normalisation fix a broken section sign?
NFC normalisation generally leaves U+00A7 unchanged. Encoding problems therefore usually come from substitution, fallback fonts, OCR, or a missing text layer rather than canonical composition. Compare visible text with extracted text, verify the intended font and licence, and test the result with assistive technology and the fonts readers are likely to use.
Font Checker Pro scans live URLs, PDFs, images, and zipped font sets to identify deployed typefaces and produce exportable audit reports for design, engineering, and compliance teams. Visit Font Checker Pro to verify your section symbols, font files, licence scope, and deployment evidence before release.
