Question 1

Which .docx structural elements does the parser use?

Accepted Answer

The model takes signal from Heading 1 / Heading 2 styles (used as section dividers), numbered lists (sequential steps), bullet lists (parallel or contextual items), and ordinary paragraph text. Hyperlinks are kept as plain text labels. SmartArt, embedded charts, and OLE objects are dropped — they're not extracted by docx parsers. The cleaner your heading-and-list structure is in Word, the closer the output matches what you'd draw manually.

Question 2

What about tables of steps inside the Word doc?

Accepted Answer

Tables are extracted row by row, but the column-vs-row distinction is partly lost — header rows become regular text. For step lists that genuinely live in a table (step number / description / next-on-yes / next-on-no), copy the table into a spreadsheet and use the Excel-to-Flowchart tool. It uses column headers to map directly to flow concepts, which produces a far more faithful diagram.

Question 3

Are tracked changes, comments, and macros processed?

Accepted Answer

Tracked changes are accepted as displayed — whatever the document currently shows is what the model sees. Comments are dropped. VBA macros are not executed and not read; only document body text is parsed. Accept or reject any pending edits and resolve comments before uploading if you want predictable output.

Question 4

What's the file-size limit and which formats are accepted?

Accepted Answer

10 MB maximum. Both legacy .doc and modern .docx are accepted, with .docx preferred because its XML structure preserves heading levels and outline numbering that improve parsing. Plain .rtf or .txt files aren't accepted here — the parser is tuned for Word-specific styles. Files larger than 10 MB are usually that size because of embedded media; extracting the procedural section into its own .docx brings the size down quickly.

Question 5

Which heading style should I use to mark sections?

Accepted Answer

Heading 1 and Heading 2 are both recognized. Heading 1 maps to top-level sections (used as flowchart titles or major branches); Heading 2 maps to sub-sections inside one diagram. Going deeper than Heading 2 is parsed but rarely affects the output, because at that depth the model treats the content as the body of the Heading 2 step rather than a new step.

Question 6

Why did the AI skip some steps that are in the document?

Accepted Answer

Usually because they were buried inside background or context paragraphs without a procedural verb in the sentence. The model picks up imperative verbs ("submit", "approve", "verify") and sequence markers ("then", "next", "finally"). If a step is hidden in a sentence like "It's important to note that the manager will sometimes…", consider rewriting it as a clear list item, then re-run. Files are processed for the single generation only and not retained.

Free Word to Flowchart Converter

A Word SOP to a flowchart

Input (.docx excerpt)

What the AI produces

What is Word-to-flowchart conversion?

Convert a Word Document to a Flowchart

Upload Word Document

AI Extracts Process

Edit and Export

Word to Flowchart Features

.doc and .docx Both Work

Heading Hierarchy

Numbered + Lettered Lists

Track Changes Ignored

Embedded Image Skipping

Multi-Column Layouts

When to use word-to-flowchart

Use this tool for

Use a different tool for

Word to Flowchart FAQ

More Free Document Converters

PDF to Flowchart

Markdown to Flowchart

SOP to Flowchart

Related guides

How to Make a Flowchart in Word: Step-by-Step Guide (+ Faster Alternative)

How to Make a Flowchart: A Complete Beginner Guide for 2026

Ready to Try the AI Flowchart Generator?