Markdown Multilevel Lists Break in Word? Fix Hierarchy, Number Continuation, and Indentation

A multilevel Markdown list can look correct in an editor and still flatten, restart, or continue incorrectly after conversion to Word. Child items may become top-level bullets, a second procedure may continue from the previous number, or a paragraph and code block may detach from the step they explain.

The problem is usually not the visible bullet symbol. It is the underlying relationship between list markers, indentation, blank lines, continuation content, and independent procedures. Word can create editable multilevel lists only when the Markdown structure is unambiguous.

First identify what the list represents

Different list purposes need different structures. Before changing indentation, decide what the list is meant to communicate.

A list should not be used merely because the source contains numbers. The intended document behavior matters more than the visible prefix.

Use stable indentation for every nested level

A child item must be indented relative to its parent. Inconsistent indentation can flatten the hierarchy or attach an item to the wrong parent.

1. Prepare the release
  - Update dependencies
    - Verify licenses
 - Run tests
2. Deploy

1. Prepare the release
   - Update dependencies
     - Verify licenses
   - Run tests
2. Deploy

Use one indentation convention throughout the document. Avoid relying on tab characters because tab stops can vary between editors and conversion tools.

Keep continuation paragraphs inside the parent item

A numbered step may contain an explanation, warning, quotation, image, formula, or code block. That continuation content must remain structurally inside the item.

1. Validate the source.

This paragraph explains the validation rules.

2. Start conversion.

1. Validate the source.

   This paragraph explains the validation rules.

2. Start conversion.

If the continuation begins at the page margin, the parser may treat it as an ordinary paragraph outside the list. In Word, that can create broken indentation or an apparent gap between the number and its explanation.

Indent code blocks, images, and quotations that belong to a step

A code block or image that belongs to a numbered instruction should use the same continuation indentation.

1. Install the package.

   ```bash
   npm install
   ```

2. Verify the installation.

   ```bash
   npm --version
   ```

Without indentation, the fenced block may end the list and cause the second numbered item to restart or become a separate sequence.

Separate independent procedures clearly

Word may continue numbering when two lists appear to belong to the same sequence. If the second list is a new procedure, make the separation explicit in the Markdown.

### Preparation

1. Back up the configuration.
2. Stop the service.

### Verification

1. Start the service.
2. Check the health endpoint.

Use one or more of these signals:

• A descriptive heading
• A sentence that introduces the new procedure
• A clear change in purpose
• A separate subsection rather than two adjacent lists

After conversion, confirm whether the second procedure restarted at 1. Word may still need a manual restart when a document combines several imported list definitions.

Do not confuse numbered headings with numbered lists

A chapter heading such as “2. Methods” should not be represented as an ordinary list item. Numbered headings belong to the document outline and table of contents.

Typing chapter numbers directly into heading text can create duplicate numbering when the Word template also enables automatic heading numbers.

Avoid manually typed sequence numbers in ordinary paragraphs

AI drafts sometimes produce numbered-looking paragraphs instead of a real Markdown list.

Step 1: Collect the files.

Step 2: Validate the files.

Step 4: Convert the files.

When the numbers are meant to update as the procedure changes, convert the content to a real ordered list:

1. Collect the files.
2. Validate the files.
3. Convert the files.

Keep fixed numbers only when they are identifiers, contractual references, test-case IDs, or another value that must not change automatically.

Reduce excessive nesting

Deep nesting consumes horizontal space and makes parent-child relationships difficult to follow in Word. Four or five levels may technically convert while remaining poor document design.

Replace deep levels when appropriate:

• Use a heading for a major subtopic.
• Use a table for repeated attributes.
• Split a long procedure into phases.
• Move explanatory detail into continuation paragraphs.
• Keep nested bullets only for genuine child actions or sub-options.

Review mixed bullet and numbered levels

A numbered parent with bullet children is often appropriate for procedures. A bullet parent with numbered children may be appropriate when each option contains an ordered sequence. The pattern should reflect meaning, not decoration.

1. Prepare the source.
   - Remove duplicate headings.
   - Check local image paths.
2. Convert the document.
   - Select the template.
   - Review conversion options.

Do not alternate bullets and numbers merely to make levels look different. Word list styling already provides visual distinction.

A practical multilevel-list cleanup workflow

1. Classify each list. Identify procedure, options, hierarchy, or fixed identifiers.
2. Normalize indentation. Apply one stable rule to every nested level.
3. Attach continuation content. Indent paragraphs, code, images, and quotations under the correct item.
4. Separate independent procedures. Add headings or explanatory text.
5. Separate heading numbering from list numbering.
6. Replace manually typed sequences. Keep fixed IDs only when intentional.
7. Reduce deep nesting. Use headings, tables, or phases where clearer.
8. Convert and review the DOCX. Check restart, continuation, indentation, and page breaks.

Review the final DOCX

Frequently asked questions

Final checklist