Technical Anshu
Tutorials Blog
🔁 File Compatibility

Moving Word and Excel Files Between Windows and Linux

Opening a file is easy. Opening it a week later, on the other system, with nothing moved - that is the real test. This guide grades what survives the Windows-to-Linux round trip and gives you the working habits that keep documents boringly reliable.

✍️ Technical Anshu🐧 Zorin OS 18⏱️ 8 minute read
🎥 Watch the video for the compatibility picture on Zorin OS 18 Pro

Mixed offices are normal now: your Zorin OS laptop, a colleague's Windows PC, a client's Office 365. Files cross between them daily. Most of the journey is safe - and the dangerous corners are specific and avoidable once you know them. Here they are, item by item.

The Round Trip Test - What Survives Between Windows and Linux
Text, tables, normal formattingTravels perfectly
Calibri font on a Linux PCSubstituted - spacing shifts
Track changes and commentsTravel well
SmartArt and fancy Word effectsOften flatten or shift
Excel pivot tablesView yes - rebuild carefully
VBA macrosDo not survive at all
👆 A file that opens is not the same as a file that survived - this is the difference, item by item
1

Fonts - the Silent Layout Shifter

The number-one cause of "your file looks different on my PC" is not the software - it is fonts. Most Office documents are written in Calibri or Cambria, which are Microsoft fonts that do not ship with Zorin OS. Linux quietly substitutes a similar-looking font, and "similar" is enough to change line breaks, table fits and page counts.

Practical fixes: install the free metric-compatible substitutes (Carlito matches Calibri's measurements, Caladea matches Cambria) so spacing survives even when the look is slightly different, or agree on a font both sides have. For anything being printed for a client, send a PDF as well as the document - a PDF freezes the layout exactly as you saw it.

2

What Travels Well

3

What Bends or Breaks

4

The Professional Workflow That Avoids 95 Percent of Pain

  1. One editor per document. A file that lives in LibreOffice should stay in LibreOffice; a client file that lives in Office should be edited in Office (web or VM). Most corruption of layout happens on the fifth crossing, not the first
  2. PDF for anything final. Quotations, certificates, print jobs - the PDF is the deliverable, the document is the source
  3. Agree the house font. If your office mixes Windows and Linux PCs, pick fonts installed on both sides and the shifting stops
  4. Test the one scary file early - your most complex document, before migration day, not during it

🎥 Watch the Full Video

See the suites and file handling in the video, then run the round-trip test on your scariest document.

▶️ Watch Full Video
❓ Frequently Asked Questions

Why does my Word document look different on Zorin OS?

Usually fonts. Documents written in Microsoft fonts like Calibri get a substitute font on Linux, which changes spacing, line breaks and sometimes page counts. Installing the metric-compatible Carlito and Caladea fonts fixes the measurements, and sending a PDF alongside freezes the layout exactly.

Can I use track changes with a colleague who is on Windows Office?

Yes. Both LibreOffice and OnlyOffice read, display and add tracked changes and comments in .docx files, so a review cycle between Linux and Windows works. Just keep one shared copy of the document rather than several versions crossing back and forth.

What happens to my Excel macros on Linux?

They do not run. LibreOffice has its own macro system but does not execute VBA, and OnlyOffice does not run VBA either. A macro-driven workbook needs genuine Excel - on Zorin OS that means the web version cannot help either; use a Windows virtual machine or keep that work on a Windows PC.

This guide is based on a Technical Anshu video • Stuck on a step? Ask in the video comments - answers happen there 🙏