Report document styles
Choose a DOCX or ODT file to count paragraph and heading styles locally.
Output
Copy or download the finished result
Documents And OCR
Style Usage Report
Report document styles locally in your browser with no server upload.
Waiting
Runs in your browser. Files do not leave your device.
Input
Style Usage Report. Count paragraph and heading styles in a local DOCX or ODT file.
Drop fileUp to 25MB. Local only.
Guide
How to use Style Usage Report
Step-by-step
- Choose or enter docx, odt in the workbench.
- Run the inspection tool locally in your browser.
- Review the style-report result, then copy or download it if the workbench offers that action.
- Use the related tools on this page for cleanup, validation, conversion, or the next step in the workflow.
Questions
Is Style Usage Report free to use?
Yes. The public tool is free to use in your browser.
Are my files uploaded?
No. This tool runs locally in your browser, so selected files or pasted input are not uploaded to Convurter.
What should I check before using the style-report result?
Style names come from package XML and may not match visual formatting if the document uses direct formatting. Review the final output before using it in production work.
What can I do after this?
Good next steps include Font Usage Report, Outline Extractor, and Document Image Report.
Workflow fit
Use Style Usage Report in the right place
If you are unsure, start from the document chooser and decide whether the job is structure review, sharing-risk review, or DOCX to PDF readiness.
Best for
- DOCX and ODT review workflows where structure, styles, fonts, images, links, tracked changes, or metadata need inspection.
- Preparing a document before conversion, upload, client delivery, or internal review.
- A focused inspect task where the expected output is style-report.
Before you start
- This tool runs in the browser, so keep the tab open until the result is created and downloaded or copied.
- Keep the editable source document available before extracting text, inspecting package data, or converting DOCX to PDF.
- Review outline, styles, fonts, images, and links before conversion because those are common sources of layout surprises.
- Check tracked-change markers and metadata before sending files that came from collaborative editing.
- Use the report as a decision aid, then route to cleanup, conversion, or verification tools if it finds something notable.
Quality checks
- Treat inspection output as a signal report, not as a guarantee that every possible issue was checked.
- Compare structure, readable text, and metadata against what the recipient should actually see.
- For DOCX to PDF, inspect the generated PDF after conversion instead of assuming office layout fidelity is perfect.
- Checksum the final shared copy when version traceability matters.
- Copy or download the result only after confirming the displayed output matches the task you intended.
Common mistakes
- Treating a package-level report as a visual layout guarantee. It is a signal, not a full office renderer.
- Converting to PDF before checking revisions, links, fonts, and embedded images can preserve problems into the final copy.
- Assuming ODT and DOCX have identical conversion support. ODT review is public; broad office conversion remains gated.
- Closing the tab before downloading or copying a browser-generated result.
- Treating the first result as final without checking the destination requirement.
Continue the workflow
Use these when the current result is only one step in a longer task.
Verify or clean up
Use these when the output needs checking, cleanup, comparison, compression, or a final share-ready pass.