Date and time of document markup is 2 hours off

I am using OnlyOffice in a Nextcloud space.
Document Server version: 9.3.1-10
Type of installation of the Document Server (docker, deb/rpm, exe, please point us to the installation guide that you used as well): deb/rpm (git)
OS: Ubuntu 22.04.5 LTS
Browser version: OnlyOffice Desktop App for Linux, Community-Version 9.4.0.129 (x64 deb)
Additional information:

Nextcloud version: 33.0.8

OnlyOffice Nextcloud App version: 10.1.2

I have uploaded a docx file to Nextcloud. It has a marked-up change that was done on 2 September 2026 5:40 p.m. CEST (3:40 p.m. UTC).

Both my local machine and the server of Nextcloud and OnlyOffice document server are in the CEST time zone.

When opening the document in the OnlyOffice web editor, it shows that the markup is from 2 September 7:40 p.m.

My suspicion for the cause: The web editor thinks the time is UTC and adds two more hours. But those two hours are already added in the original file.

By the way, the error only shows in mark-up. The times in comments are shown correctly. Once I add mark-up in the OnlyOffice editor, times are also displayed correctly.

What I already tried to narrow down the problem: Create the marked-up document in different editors (Microsoft Office, TextMaker, LibreOffice, using both Windows and Linux as operating system), open the document up in a different browser (Vivaldi), even uploading the document to a different Nextcloud server running EuroOffice → in all cases, the error persisted. The behavior is the same when I open the local file in the OnlyOffice desktop app. I can consistently reproduce the error with every docx file I create and mark-up.

Is this a bug in the OnlyOffice web editor, or a limitation of the used file format (docx) - or both?

Hi @eunic, welcome to the community!

Thanks for the report — your suspicion is right. The editor reads the revision time from the file as UTC and adds your local offset on top. Markup made in ONLYOFFICE displays fine because we write and read it the same way, and comments use a different path.

Known issue, already tracked. We’ll update the thread once it’s fixed.