Rixoffice Documentation
File Formats

Rixoffice DOCX Compatibility: Open and Save Word Files

Published September 4, 2026Updated September 4, 20266 min read

How Rixoffice opens .docx and .doc files and saves Word documents with byte-preserving fidelity, keeping charts, math, watermarks and protection intact.

On this page

Rixoffice treats .docx as its home format. You can open a Word document created anywhere, edit it in RixDocs, and save it back to the same file without losing the parts you did not change. The docx engine inside Rixoffice parses OOXML, patches only what you edited, and writes the package back with byte-preserving care — so styles, charts, headers and everything else survive the round-trip.

Opening Word documents

Rixoffice opens Word files directly. There is no import dialog, no conversion wizard and no converted copy left behind:

  • .docx — modern Word documents open natively in RixDocs with full fidelity.
  • .doc — legacy Word 97-2003 files open through a compatibility filter, then behave like any other document.

To open a file, press Ctrl+O (Cmd+O on Mac), drag it onto the Rixoffice window, or double-click it in your file manager if Rixoffice is your default app for .docx. The document opens in a tab alongside anything else you have running, so a report, its data workbook and the matching deck can stay open at once.

What you see after opening

RixDocs renders the document with the same structure Word uses: styles, section breaks, headers and footers, footnotes, tables, images and charts all appear in place. The ribbon exposes the familiar Home, Insert, Layout, Design, References, Review, View and Draw tabs, so editing feels immediate rather than like learning a new tool.

Saving without re-writing your file

Most editors regenerate the entire document package every time you save, which is exactly where formatting quietly dies. Rixoffice takes a different approach: byte-preserving paragraph patching. When you press Ctrl+S, the docx engine:

  1. Parses the existing .docx package and keeps every part it does not need to change.
  2. Rewrites only the paragraphs, runs or properties you actually edited.
  3. Splices the patched content back into the original package.
  4. Saves the file in place, preserving the parts Word wrote originally.

The practical result: your company template keeps its theme, a scanned signature stays where it was placed, review markup you never opened remains intact, and fields, bookmarks and custom XML ride along untouched.

What the docx engine keeps intact

FeatureHow Rixoffice handles it
Styles and themesPreserved; your edits reuse the styles already in the file
ChartsNative OOXML charts round-trip and stay editable
EquationsMath (OMML) is preserved and can be edited
Document protectionProtection flags and settings survive saving
WatermarksKept in the header parts where they belong
TIFF and metafile imagesRead, displayed and written back without conversion
Headers, footers, footnotesPreserved, including per-section variations
Comments and revisionsKept so review workflows keep working

Working with protected and template files

Protected and watermarked files are everyday traffic in legal, finance and government work. Rixoffice opens them the way Word does: if a document is protected, the protection carries through; if the file carries a watermark in its header, the watermark stays put while you edit the body. Because the engine patches rather than rewrites, you can fill in a contract template and hand back a file that still matches the template it came from.

The same logic applies to documents with heavy front matter — cover pages, tables of contents, citation fields. Open, edit chapter five, save, and the front matter is still exactly the machine-written original.

A safe round-trip in five steps

  1. Open the .docx in Rixoffice from the Home screen, with Ctrl+O, or from your file manager.
  2. Edit normally — text, tables, styles, charts, anything on the ribbon.
  3. Press Ctrl+S (Cmd+S on Mac). The patched file saves in place; there is no "keep format?" warning because .docx is native here.
  4. For a separate copy, use File, Save As and pick a new name or folder.
  5. Open the result in Word on any machine to confirm: the parts you never touched are the parts Word wrote.

Choosing other output formats

.docx is the format Rixoffice knows best, but it is not the only exit. Use File, Export as PDF when you need a locked, print-ready copy from RixDocs or RixSlides. In Markdown Studio you can write in Markdown and export to DOCX through the same docx engine, which turns plain notes into a properly formatted Word document. Legacy .doc files are covered in the legacy formats guide.

What to explore next

Quick steps

  1. Open the .docx from the Rixoffice Home screen, with Ctrl+O, or by double-clicking the file.
  2. Edit normally in RixDocs — text, tables, styles, charts, anything on the ribbon.
  3. Press Ctrl+S (Cmd+S on Mac) to save the patched file in place.
  4. Use File, Save As to write a separate copy with a new name or folder.
  5. Use File, Export as PDF when you need a locked, print-ready version.

Frequently asked questions

Can Rixoffice open Microsoft Word .docx files?

Yes. Rixoffice opens .docx files natively in RixDocs with full fidelity — styles, tables, charts, headers, footnotes and images all appear where Word put them. No conversion step or imported copy is created.

Will my formatting survive after saving from Rixoffice?

Yes. Rixoffice saves .docx with byte-preserving paragraph patching: the engine rewrites only the parts you edited and keeps the rest of the original package exactly as it was, so styles, themes and untouched content survive round-trips.

Does Rixoffice support legacy .doc files?

Yes. Legacy Word 97-2003 .doc files open through a compatibility filter and behave like any other document in RixDocs. When you save, Rixoffice writes a modern .docx so nothing is trapped in the old format.

What Word features does the docx engine preserve?

The docx engine keeps native OOXML charts, math equations, document protection, watermarks, headers and footers, footnotes, comments, revisions and TIFF or metafile images intact, because it patches the existing package instead of regenerating it.

Related documentation