AffinityOnLinux: A Compatibility Guide for GNU/Linux

What AffinityOnLinux Solves

AffinityOnLinux addresses a distribution gap rather than providing a new Affinity editor. Affinity applications are Windows software, while many GNU/Linux users manage Windows applications through WINE, a compatibility layer. This repository gathers instructions for placing Affinity Photo, Designer, and Publisher within that compatibility environment.

The intended audience is a Linux user who already has access to Affinity through an appropriate source. The README links to Affinity by Canva and Serif's Version 2 pages, but it does not describe this project as an installer for obtaining or activating the software. Those links identify the official application ecosystem. The repository supplies compatibility information, setup guides, known issues, and links to support channels.

Several WINE managers are covered. The README recommends Wine 10.17+ for users comfortable with the terminal. It also provides guides for Lutris, Heroic Games Launcher, Bottles, and Rum. That choice matters because the repository does not present one universal launch method. The installation experience depends on the manager and on the Linux distribution being used.

The repository also distinguishes its own methods from two unofficial alternatives. It links to an AppImage and Python GUI installer maintained by ryzendew and a Nix method maintained by mrshmllow, but says that AffinityOnLinux and its Discord do not directly support those projects. Users looking for help with either method are directed to the respective authors.

The WINE Compatibility Path

The central mechanism is WINE. According to the README, the repository contains information for getting Affinity software working on GNU/Linux with WINE, rather than a native Linux build of the applications. The repository layout reinforces this design. Its top-level entries include Guides, FAQ.md, Roadmap.md, Credits.md, and Assets, with separate guide directories named for Wine, Lutris, Heroic, Bottles, and Rum.

The documentation is organized as a selection path. A user first checks whether the Linux distribution is compatible in the FAQ. The user then chooses a WINE manager. Finally, the user opens the guide for that manager. This is a documentation-driven setup flow, not a claim that AffinityOnLinux contains a single executable that performs every installation step.

The Wine guide is marked as suitable for users comfortable with terminal work. The Lutris guide is described as a graphical option, while Rum is also described as terminal-based. The README does not show the internal commands, configuration files, prefix details, or application startup sequence for any of these methods. Those details are delegated to the linked guides, so the repository-level README cannot establish whether a particular guide uses a shared prefix or whether each application receives a separate environment.

This distinction matters for engineers assessing the project. AffinityOnLinux is best understood as a compatibility knowledge base with manager-specific procedures. It may reduce the need to assemble a WINE setup from unrelated documentation, but it does not remove the work involved in managing Windows application dependencies.

Installing Through the Selected Wine Manager

The README does not provide a complete installation command or configuration snippet, so its top-level guide does not support reproducing the installation from a single block. It directs users to the manager-specific guide and identifies the first checks to perform.

The documented sequence starts with the FAQ compatibility check:

> Check if your Linux distribution is compatible.

The README then asks the user to select a WINE manager. Wine 10.17+ is the recommended guide for users comfortable with the terminal. Lutris is recommended when a graphical WINE manager is preferred. Heroic Games Launcher, Bottles, and Rum have their own linked guides.

For a first real use, a reader should open the guide corresponding to the selected manager, follow its setup procedure, and use the official Affinity download or update links listed by the README rather than assuming that the repository contains the application binaries. The repository links to Affinity by Canva and Version 2 pages, then separately links to Windows update pages for Photo, Designer, and Publisher.

The README does not document a rollback command, a post-install verification command, a supported kernel version, or a universal launch command. It also does not state that every guide supports every Affinity application. Those omissions mean that the first-use tutorial has to stop at the documented handoff into the manager-specific file. A user who expects a single cross-distribution command will not find one in the README.

Known Issues That Affect Adoption

The Roadmap records limitations that are directly relevant to an adoption decision. Sign-in for Affinity by Canva is not working at the moment, and the repository says it is looking for solutions. That issue can affect a core account-dependent workflow even if the application starts successfully.

UI settings also do not save, according to the README. The repository provides a workaround in Guides/Settings.md, but the existence of a workaround does not establish that the underlying behavior is resolved. Users who depend on repeatable interface configuration should read that file before deciding whether the current method meets their needs.

There is also an Affinity V1 issue involving purchases made through the Windows Store. The README links to the FAQ for the versions that are supported. It does not explain whether the issue affects all Windows Store purchases, all V1 installations, or only a particular acquisition path. That uncertainty should be checked in FAQ.md rather than inferred from the release labels.

These are compatibility constraints, not merely cosmetic bugs. The project is therefore a poor fit for a user whose workflow requires dependable Canva sign-in or persisted UI settings and who cannot accept a workaround or unresolved behavior. It may still be suitable for users who can work around those issues and use the documented manager guides.

Wine Manager Guides Compared

AffinityOnLinux does not force a single WINE manager. Its choice reflects different operating preferences. The Wine 10.17+ guide is the recommended path for terminal-comfortable users and provides a direct route based on Wine itself. Lutris is the documented recommendation for users who want a graphical WINE manager. Heroic Games Launcher, Bottles, and Rum are additional choices with separate guides.

The actual difference between these paths is not described in the top-level README. It does not compare graphics-driver settings, update behavior, storage locations, or how each manager handles the Affinity installation. It would therefore be unsafe to claim that one manager has better application compatibility or simpler upgrades based on this repository alone. The correct comparison begins with the corresponding guide under Guides.

The README explicitly describes the Wine guide as suitable for users comfortable with the terminal, the Lutris guide as suitable for users wanting a graphical WINE manager, and Rum as terminal-based. It does not provide equivalent detail for Heroic Games Launcher or Bottles. Users should not infer that the guides behave identically. Manager selection is a compatibility decision rather than a cosmetic preference, and failures should be reported through the repository's Issues or Discord channels.

Maintenance, Licensing, and Support Boundaries

The repository is not archived, and the last push was on 2026-08-22. That is the maintenance information stated by the repository facts. Recent release entries include staged and preview releases, including v10.19-staged (GameDirectionWine-x86_64), v10.18-staged (GameDirectionWine-x86_64), and v10.16-644-g8d61f4c3735-preview (ElementalWarriorWine-10.16-8d61f4c3735-x86_64). The release names indicate that WINE-related artifacts and preview naming are part of the project's changing setup surface.

The repository uses GPL-2.0. That license applies to the material in this repository, but the README does not state what additional terms govern the Affinity applications or downloaded installers. This article does not interpret those terms or provide legal advice. Users should separately review the licensing and download conditions for the Affinity software they obtain.

Support is community-oriented. The README points to GitHub Issues and Discord, and asks users with guide fixes to submit pull requests. It also warns that the unofficial AppImage, Python GUI, and Nix methods are not officially supported by this repository. The support boundary matters: a failure in an external installer should be raised with that installer's maintainers, not assumed to be covered by AffinityOnLinux.

Editorial conclusion

AffinityOnLinux is appropriate for GNU/Linux users who already have a legitimate Affinity installation and need a WINE-based setup guide. It is not a replacement for official Affinity distribution, a native Linux port, or a support channel for every third-party installer. Before adopting it, verify your Linux distribution in FAQ.md, confirm that the selected WINE manager has a guide in this repository, and inspect Roadmap.md for unresolved sign-in or settings issues.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-2.0
3. README
4. Releases
5. seapear/AffinityOnLinux on GitHub