Format Atlas

Guides

Choose a document editing format

Use DOCX or ODT for formatted collaboration according to the recipient's tools, Markdown for versioned technical text, and TXT for plain characters.

Which format should you choose?

Choose by the role each file plays in your workflow.

  • Collaboration centered on Word → DOCX
  • Collaboration with OpenDocument support → ODT
  • Technical writing and version history → Markdown
  • Simple text without formatting → TXT

Choose for the editor and the final output

Editable sources and final delivery files serve different purposes. Check the recipient's app, formatting requirements, and how revisions will be tracked.

Formats to consider

DOCX

Good for: Collaborative editing of tables and images in Word-based workflows

Less suitable for: Technical writing managed through text diffs

ODT

Good for: Editable document exchange with OpenDocument-supported tools

Less suitable for: Transfer without knowing the recipient's app

Markdown

Good for: Text-based technical documents and version control

Less suitable for: Delivery with a completely fixed appearance

TXT

Good for: Simple character information without formatting

Less suitable for: Documents needing headings or tables

Before you export

  • DOCX may display differently across apps.
  • Check the Markdown dialect and rendering environment.

Related comparisons

PDF vs DOCXPDF is suited to distributing a reviewed page layout; DOCX is suited to creating and revising a document. Choose by what the recipient needs to do.TXT vs MarkdownTXT stores unformatted text, while Markdown adds lightweight notation for document structure. Both remain plain text, but Markdown's headings, links, and code markers need a compatible renderer to appear formatted.

Guides

Choose a document delivery formatFor document delivery, decide whether the recipient needs a fixed presentation or an editable source.Checking versions, display and hidden data before document handoffSeparate editable originals and viewing copies, inspect revision history and dependencies, then test display and re-editing in the recipient's application.

References and specifications