Turn a Word document into JSON that keeps its structure
Convert a Word document to JSON with headings, lists and tables as nested keys. Names, figures and dates stay as written. Paste text or drop a file.
This preview shows the first 350 words and does not keep your file.
Need a different result? Turn anything into anything: drop any file, pick what you want out of it.Try it →A Word document is written to be read, so its meaning lives in headings, indented lists and tables that a program cannot see. Rebuilding that by hand as data means retyping every name and figure and guessing at the nesting. This page converts the document into one JSON object that follows its sections, lists and tables, and keeps names, figures, dates and section order exactly as written.
What you get
Headings become keys
Each heading becomes a snake_case key and the text under it becomes the value, so the order of the sections in your document is the order of the keys.
Lists and tables kept whole
Bulleted and numbered lists become arrays. Tables become arrays of objects, with the header row used as the field names.
Values as written, null when missing
Names, figures and dates are copied exactly as they appear. If the document leaves a field blank, the value is null rather than a guess.
How it works
- Step 1
Paste the text of your Word document, or drop the .docx file into the box.
- Step 2
Read the JSON preview, which shows the top of the result with its keys and nesting.
- Step 3
Create a free account to get the whole JSON and a .json download, plus longer and scanned files, batches, and changes to the field names or schema you need.
Who uses it
Developers loading document content into an app
Get a document's sections and tables as structured data that an API or database import can read directly.
Operations staff moving filled-in forms into systems
Turn a signed agreement, order form or policy into records that use the same field names each time.
Editors checking how a document is organised
See the document as a nested tree, so a missing section or a figure sitting under the wrong heading is easy to spot.
Questions
How does the Word document become JSON keys?
Headings become snake_case keys, paragraphs under a heading become their value, bulleted and numbered lists become arrays, and tables become arrays of objects using the header row as field names. Nested headings become nested objects.
Does the output keep the order of the sections?
Yes. The keys and arrays follow the order in which the sections, list items and table rows appear in the Word document, so reading the JSON from top to bottom matches reading the document.
What happens to a Word file that is a scan or has images of text?
Text typed in the document is read directly. Pages that are scanned images need OCR to read the text, and OCR is included with a free account. Text inside images is not read in the preview.
Can I rely on the JSON without checking it?
Not always. Results can contain mistakes, such as a figure misread or a line placed under the wrong heading, so check the JSON against the original Word document when names, amounts or dates matter. The preview reads up to about 6,000 characters and does not keep your file.
Related tools
See it on real examples
Three actual runs of this tool. Open one to see the input and the whole result.