**`<h5>`** exists for completeness in the six-level heading system, but in practice most pages never need to go this deep — reaching `<h5>` usually signals either an unusually long, deeply structured reference document (like a technical spec or a legal contract with many nested clauses), or a sign that the content should be reorganized into separate pages or simpler lists instead of ever-deeper headings.
1Understanding <h5>
`<h5>` exists for completeness in the six-level heading system, but in practice most pages never need to go this deep — reaching <h5> usually signals either an unusually long, deeply structured reference document (like a technical spec or a legal contract with many nested clauses), or a sign that the content should be reorganized into separate pages or simpler lists instead of ever-deeper headings.
Before using <h5>, ask whether the same information would read more clearly as a bold lead-in inside a paragraph, or as a definition list (<dl>) entry, rather than another heading level.
<h4>HTTP Status Codes</h4>
<h5>4xx Client Errors</h5>
<p>...</p>
<h5>5xx Server Errors</h5>
<p>...</p>2Practical Example
Here is a real-world application of <h5> showing how it is used in production HTML.
<!-- A long legal/reference document with deep nesting -->
<h3>Section 3: Definitions</h3>
<h4>3.1 General Terms</h4>
<h5>3.1.1 'Agreement' means...</h5>3Best Practices
Follow these guidelines when working with <h5>:
1. Reserve <h5> for genuinely deep, long-form reference content
2. Consider whether a <dl> or bold lead-in text communicates the same structure more clearly
3. Keep the heading hierarchy unbroken — don't use <h5> without an <h4> above it
Tip: Before using <h5>, ask whether the same information would read more clearly as a bold lead-in inside a paragraph, or as a definition list (<dl>) entry, rather than another heading level.
<h4>HTTP Status Codes</h4>
<h5>4xx Client Errors</h5>
<p>...</p>
<h5>5xx Server Errors</h5>
<p>...</p>