If the entire ONLYOFFICE window looks soft, test Linux display scaling before changing font files or Fontconfig settings. If only text inside a document looks wrong, check whether the document uses a font that is missing or substituted on your computer. These are different problems and need different fixes.
Close and reopen ONLYOFFICE after each change, then inspect the same document at the same window size. This simple comparison helps you avoid changing several settings at once and makes it clear which change mattered. If you are unsure whether the issue is specific to the editor, compare small text in another desktop application on the same display.
Blurry edges across menus, toolbar labels, and document text often point to display scaling or how the application is being displayed. Fractional scaling, such as 125% or 150%, can be a factor on some Linux desktop and graphics combinations. It is not proof of a universal ONLYOFFICE defect: display server, desktop environment, package format, graphics driver, and app version all affect the result.
For a quick test, open your desktop environment’s Display settings and temporarily switch to a standard scale such as 100% or 200%, if those choices fit your screen. Sign out and back in if your desktop requires it, then launch ONLYOFFICE again. On GNOME, the relevant control is under Settings > Displays; other desktops use different names and may offer different scale increments. If the application becomes sharp at a standard scale, the blur is likely tied to fractional scaling or the display path. Choose the clearest usable scale as a practical workaround, or check your desktop’s current documentation for supported HiDPI options.
You can identify the session type from a terminal with echo "$XDG_SESSION_TYPE". The result is commonly wayland or x11. This does not diagnose the graphics stack by itself, but it gives useful information if you need to compare behavior between sessions or report a reproducible issue. Do not copy old GNOME commands that enable experimental fractional-scaling features without checking the documentation for your installed GNOME version; available settings have changed over time.
An ONLYOFFICE Desktop Editors issue documents a particular GNOME 45 Wayland case at 125% fractional scaling where the reporter saw a blurry interface and document, while reporting different behavior on KDE Wayland. Treat that report as evidence that the symptom can depend on the environment, not as a guaranteed fix for every Linux system. See the ONLYOFFICE report about GNOME fractional scaling.
ONLYOFFICE has an application interface scaling option on Linux, and its release history records support for interface scaling values including 125%, 150%, and 175%. The exact controls may vary by release. Open the application’s settings and look for the interface or application scaling control; if the label or location differs, consult the help for your installed version instead of relying on a menu path from an older release.
Change only the application interface scale for a test, then restart the editor if requested. Interface scaling changes the size of application controls. Document zoom changes how large the page appears inside the editor. Increasing document zoom can make letters easier to read, but it will not repair fuzzy toolbar text or low-resolution scaling of the whole window. Conversely, reducing interface scale may make controls sharper in one setup while making them too small to use. Pick a setting that remains readable and compare both the toolbar and the page.
For background, the ONLYOFFICE Desktop Editors changelog records 125% and 175% interface scaling support for Linux and, in an earlier release entry, 150% support. The currently listed changelog version at the time this article was checked is 9.4.0, released May 19, 2026. That page does not establish that every fractional desktop scale works equally well on every distribution.
If menus look crisp but a particular document has fuzzy, unusually wide, or visibly different letters, inspect its font family. A document may name a font that is not installed on your Linux system. The editor then has to display a substitute, which can change letter shapes, line breaks, page count, and spacing. A different layout is not the same as blurry screen rendering, but a substitute face can make the text look wrong enough to be mistaken for a rendering problem.
In a terminal, check a font family used by the document with Fontconfig’s matching tool. For example:
fc-match ArialThis prints the font Fontconfig matches for that family. If you are checking a multiword font name, put it in quotes, as in fc-match "Liberation Serif". A substitute result does not necessarily mean ONLYOFFICE uses precisely the same fallback in every part of its rendering pipeline; it is a practical check of the fonts available to the Linux font system.
Install the needed typeface from a trusted source and make sure its license permits your use. ONLYOFFICE documents per-user font locations such as ~/.local/share/fonts and the system-wide /usr/share/fonts/ directory. For a personal installation, copy a supported font file into a subfolder of ~/.local/share/fonts, then refresh the user font cache with fc-cache -f. A distro package or its graphical font manager may be safer and easier, especially for system fonts. Avoid downloading font bundles from unknown sites or replacing system font directories.
After installing a font, completely close and restart ONLYOFFICE. The official ONLYOFFICE instructions for adding fonts also say to restart the editors after installation. Reopen the same file and check whether the selected font is now available in the font list and whether the text layout matches expectations.
Fontconfig maintains font information and cache files. If you just installed, removed, or updated fonts but applications still do not see the change, refresh the cache and restart ONLYOFFICE:
fc-cache -fOn systems where you installed fonts globally, your distribution’s package manager may update font caches as part of installation. Running this command is a reasonable refresh step, but it will not correct blur caused by fractional display scaling, a compositor, or a graphics driver. Do not delete Fontconfig cache directories as a first response. The Fontconfig user documentation describes the configuration and cache locations, and notes that some older per-user locations are deprecated.
If the issue affects the whole editor at ordinary scaling, update ONLYOFFICE Desktop Editors using the same supported installation channel you already use, then retest. The official ONLYOFFICE getting-started page links to Linux installation guidance. AppImage users need to download a newer AppImage to update, according to the official AppImage instructions. Avoid mixing packages from different channels while troubleshooting; first confirm which build you launch from your application menu or terminal.
Now create a blank document with a common installed font and compare it with the affected file. If the blank document is sharp but one file is not, concentrate on that file’s font choices, embedded images, and zoom. If every file and every part of the application remains blurry, the evidence points back toward scaling or the Linux graphics/display path. A one-time export to PDF can help you distinguish the on-screen preview from the document output, but it is not a complete screen-rendering test: PDF viewers and printers use their own rendering paths.
fc-match to check the named font, install the licensed font if needed, refresh discovery, and restart the editor.There is no single Linux font-rendering switch that fixes every case. The reliable endpoint is a repeatable comparison: the same text looks crisp at a usable scale, expected fonts are available, and document layout remains correct. If changing system scale fixes the window but makes other applications impractical, keep that observation and report the environment details to the ONLYOFFICE project or your distribution’s support channel rather than making broad, permanent font configuration changes.
Create an Outlook meeting invite, add required or optional attendees, choose a time, add Teams details, set recurrence, and check replies in new or classic Outlook.
Use Excel's Data Validation settings to set a maximum, minimum, exact length, or character range, then add clear prompts and error alerts.
Fix the Outlook “We can’t schedule the meeting” error by checking account support, refreshing Teams sign-in, and repairing the Classic Outlook add-in.
Change Office 365 menus, spelling and grammar settings, or keyboard input in desktop apps and Microsoft 365 for the web.
Learn how to auto-forward all or selected emails in Outlook 365 using Forwarding settings or Rules, plus how to stop forwarding and fix blocked external forwards.
Use Microsoft Editor in Word for Microsoft 365 to check spelling, grammar, clarity, and conciseness, review suggestions, and tune proofing settings.
Learn how to add an RSS feed to Outlook 365 in classic Outlook for Windows, find the correct feed URL, manage subscriptions, and fix common RSS issues.
Jump straight to any page in Word for Microsoft 365 with Ctrl+G or F5, relative page numbers, or the Navigation pane, with Windows and Mac shortcuts.
Learn how to add contacts to Outlook on the web, new Outlook, classic Outlook, and mobile, plus how contact syncing and CSV imports work.
Change a Word page color, add a picture background, remove either, and enable background printing on Windows or Mac with clear, current steps.
