Guides for spreadsheet installs
Long-form how-tos for verified DesktopEditors installs. Start at the home install panel when you only need the command, then use these pages for OS detail, migration, and safety notes that outgrow a single panel.
Each guide answers one primary question in the opening lines, then walks the verified door for that job. Prefer GitHub Releases, winget ONLYOFFICE.DesktopEditors, or brew cask onlyoffice. Skip portal wrappers that rename setups for ad ranking.
Keep one update door per machine after the first successful save. Record winget, brew, or the Releases filename on a desk card so the next person inherits a clear path instead of a Downloads folder full of mystery installers.
Install by operating system
Step-by-step installs with DesktopEditors_x64.exe, winget, brew, and AppImage doors.
- Windows installRun winget or DesktopEditors_x64.exe from the current DesktopEditors tag to install on Windows.
- macOS installRun brew cask onlyoffice or open the matching ONLYOFFICE dmg from DesktopEditors releases on macOS.
- Linux installDownload DesktopEditors-x86_64.AppImage or the amd64 deb from the current DesktopEditors tag on Linux.
- Debian packageUse onlyoffice-desktopeditors_amd64.deb from the current DesktopEditors tag on Debian or Ubuntu.
Comparisons
Local desktop clients against browser workbook tabs.
Switch and import
Leave cloud workbook tabs for a desktop file on disk.
Setup and security
First run, formats, updates, and how the safety model works.
- Is it safe?An install is safer when you use GitHub Releases or verified winget and brew ids and avoid portal wrappers.
- First runOn first run after install, launch the editors, create a sample workbook, save locally, and write down your update door.
- FormatsAfter you install Desktop Editors, .xlsx is the everyday interchange format for opening and saving workbooks you control.
- Update and uninstallUpdate with the same door you used originally, and uninstall with winget, brew, or OS remove tools when the desk retires.
Cluster pages cover releases, GitHub layout, download-safe habits, and first-computer setup. Trust pages explain who publishes this documentation and how facts are verified against upstream sources.