Download the build for your computer
Get GenOffice from the genspark-ai/genoffice releases page. The desktop app opens and saves Office documents locally; its AI features have separate account or provider requirements. You can check a small local document before connecting any AI service.
This guide uses v0.12.29, released October 22, 2026. The release assets and the repository's platform requirements were checked on October 23. Use the installer that matches both your operating system and processor.
| Computer | Package to choose | Documented requirement |
|---|---|---|
| Mac with an Apple chip | GenOffice-0.12.29-arm64.dmg |
macOS 11 or later |
| Intel Mac | The x64 .dmg asset |
macOS 11 or later |
| Most Windows PCs | The x64 .exe installer |
Windows 10 or later |
| Windows on Arm | The arm64 .exe installer |
Windows 11 on Arm |
| Debian or Ubuntu, x86_64 | The .deb asset |
glibc 2.34 or later |
| Fedora, RHEL or openSUSE, x86_64 | The .rpm asset |
glibc 2.34 or later |
| Other compatible x86_64 Linux systems | The .AppImage asset |
glibc 2.34 or later and FUSE 2 |
On a Mac, About This Mac identifies the chip or Intel processor. On Windows, inspect Settings, System, About, System type. A matching filename matters more than choosing the first download in the asset list. GitHub's source archives contain code; they are not the desktop installer.
Install without replacing your documents
On macOS, open the downloaded disk image and copy GenOffice into Applications. On Windows, run the matching official installer and follow its prompts. Keep your existing office application available while checking the new editor. Use copies of documents for the first test.
For Debian or Ubuntu, the upstream installation command is:
sudo apt install ./genoffice_<version>_amd64.deb
Replace the filename with the package you actually downloaded. For Fedora or RHEL, the documented equivalent is sudo dnf install ./genoffice-<version>.x86_64.rpm; openSUSE uses sudo zypper install with that RPM. These commands install software system-wide. Our test below did not run the Windows or Linux installers.
An AppImage needs the appropriate FUSE runtime, executable permission and a compatible system. Follow the repository's Linux instructions for your distribution. If an installer fails, first compare its architecture and OS requirements. Do not solve a mismatch by downloading an unofficial repack or disabling your computer's security checks.
Create a small document and read it back
The bundled command line provides a repeatable first document test. It uses the same document engines without requiring an AI-generated draft. The official CLI reference documents its installation and commands.
Open a terminal in a new test folder. First check discovery:
genoffice --version
For the tested release, this prints genoffice 0.12.29. If macOS reports that the command is missing, use the launcher inside your installed application:
"/Applications/GenOffice.app/Contents/Resources/cli/genoffice" --version
Use that full launcher path in place of genoffice in the following commands if needed. On Windows, open a new terminal after installation so it receives the updated PATH. A missing command does not by itself mean the document editor failed to install.
Save this plain-text Markdown as notes.md in your test folder:
# WebFV local document check
This file was created for a software test.
- Keep a separate copy.
- Reopen and check the saved text.
Create the Word document, then inspect the saved file in a separate command:
genoffice create --type docx --from notes.md --out notes.docx
genoffice info notes.docx --json
genoffice docs read notes.docx --range 0-4 --json
genoffice docs check notes.docx --json
In our test, creation exited successfully and produced a 3,628-byte DOCX. Reading it back returned the heading, paragraph and both list items shown above. The document check reported no issues across its ten checks. This verifies the small file's creation and text readback. It does not certify the visual layout of an arbitrary Word document.
The range matters: copying the README's --range 0-9 example onto this short document returned an out-of-range error. The valid range was 0-4. Use the range returned for your document rather than assuming every file contains ten readable blocks. The info summary counted six blocks, while docs read exposed five body blocks in this example; do not derive a read range from the former count alone.
Open the result before using it for real work
Open notes.docx in GenOffice or your usual Word-compatible editor. Check the heading, paragraph and bullets. For an existing document, work on a copy, make one obvious edit, save it and reopen the saved copy. Compare the changed text and the parts you did not intend to change.
For spreadsheets, inspect formulas as well as displayed values. For presentations, check slide layouts and fonts. A successful save proves a file was written; it does not establish complete Microsoft Office compatibility. Keep the original until the saved copy passes the checks that matter for your work.
Our reproduced test used the official arm64 package's CLI with Node 24.5.0 on macOS 26.6.2. We ran it from a mounted installer in a temporary directory. We did not install into Applications, test the desktop save dialog, render the document, or test Windows and Linux. The platform table follows upstream documentation.
Keep local editing and AI access separate
GenOffice's open-source desktop application is free to use. The repository distinguishes local document editing from AI calls that use a Genspark sign-in or a configured provider. Provider availability, quotas and charges are separate from downloading the app. None of those services was needed for the example above.
If your task is editing a PDF rather than producing an Office document, the PDFCraft save checklist explains how to verify that an exported PDF contains the change. For GenOffice errors, retain the app version, OS, command or editing action, and a small non-private sample when reporting the problem through its repository.