Customising Gala in elementary OS for better animations and effects

elementary OS has earned a reputation as one of the more polished Linux distributions, and at the centre of that experience sits Gala, its window manager and compositor. Most users rarely think about Gala until they want to change how a window slides into view or how the workspace switcher behaves. The good news is that under the calm Pantheon surface, Gala exposes a surprising number of knobs worth turning, and Australians who enjoy tinkering with their setups have a healthy tradition of doing exactly that.

Across community meetups in Brisbane, Melbourne and Sydney, and at annual gatherings such as Linux Conference Australia (which rotates through cities including Hobart, the Gold Coast and Canberra), elementary OS users often swap notes about visual tweaks. The same spirit carries through to online forums, where someone in Adelaide shares a dconf snippet and a mate in Perth chimes in with a small refinement. This guide collects the kind of practical adjustments that come up in those conversations, written with Australian English conventions and with an eye on the realities of local hardware and connectivity.

The following sections cover how Gala handles animations, where its effects come from, and how to tune them safely. You will learn how to adjust speeds via dconf, enable Mutter's experimental blur, remap window-management shortcuts to suit your workflow, and keep things responsive on older laptops — especially relevant during an Australian summer when thermals can throttle a machine quickly.

Before changing anything, it helps to remember that almost every tweak described here is reversible. Taking a quick dconf dump beforehand gives you a one-command escape hatch if a setting produces something you do not like.

Understanding Gala and its compositing engine

Gala is built on top of libmutter, the same compositing library that powers GNOME Shell. That relationship matters because many of the more interesting visual options in Gala actually live in the Mutter schema, not the Pantheon one. When you read about "experimental features" or "animations" in elementary OS documentation, you are usually looking at settings stored under org.gnome.mutter, while core Gala behaviour lives under org.pantheon.desktop.gala.

For most users, the practical upshot is that there are two main ways to edit these settings. The first is dconf-editor, a graphical tool you can install from the AppCentre or via apt. It presents every available key as a checkbox or slider and is the friendliest entry point. The second is the gsettings command-line tool, already present on every elementary install. Running gsettings list-keys org.pantheon.desktop.gala in a terminal prints every available option for Gala; doing the same with org.gnome.mutter reveals the upstream settings it inherits.

A third route is elementary-tweaks, a community-maintained extension that adds a Tweaks pane to system settings. It exposes a curated subset of the options that would otherwise require dconf-editor, which is handy if you only want common adjustments. For deeper changes, though, dconf-editor and gsettings remain the most direct path.

Adjusting animation speed and behaviour

The single most popular change Australians tend to make first is speeding up window animations. By default, Gala uses a fairly gentle curve when minimising, maximising or opening new windows. On an older ThinkPad that doubles as a home-office machine in Perth, or on a small ASUS laptop used at a kitchen table in Geelong, that default can feel a touch ponderous.

The relevant key sits under org.pantheon.desktop.gala.animations. Setting enable-animations to false turns off transitions entirely, which is the fastest option but loses some of the desktop's character. A more nuanced approach is to leave animations on but adjust the upstream Mutter setting org.gnome.desktop.interface enable-animations, combined with the experimental flag inside org.gnome.mutter.experimental-features.

You can also tweak how long individual transitions take. Mutter's experimental schema exposes duration-related keys that affect fade-in, fade-out and workspace switching. The exact key names have shifted across elementary OS releases, so the safest pattern is to open dconf-editor, navigate to org.gnome.mutter.experimental-features, and tick the boxes one at a time while watching the effect. Restarting Gala with nohup gala --replace & in a terminal, or simply logging out and back in, applies changes cleanly.

For Australian users on metred NBN plans or congested evening connections, animations do not affect network use, but they do affect how snappy the desktop feels when the machine is under load. A shorter duration often pairs well with disabling the window-open "bounce" effect, one of the few transitions many power users turn off first.

Enabling blur, edge tiling and other experimental effects

The Pantheon desktop is intentionally restrained, but Mutter's experimental features can add a little extra polish without overwhelming the look. Two stand out: dynamic workspace blur and edge-tile snapping. Both are toggled from the same experimental-features string, which holds a space-separated list of enabled flags.

Setting org.gnome.mutter.experimental-features to include blur enables a subtle frosted-glass effect behind windows on the workspace overview. It looks particularly nice on machines with high-DPI screens, common among the Dell XPS and Lenovo Yoga models widely sold through Australian retailers. To enable it from a terminal:

gsettings set org.gnome.mutter.experimental-features "['blur', 'edge-tile']"

The order does not matter, and you can remove a flag by rewriting the list without it. Edge-tile adds a small snap zone when you drag a window against the screen edge, useful if you have grown used to tiling workflows on other platforms.

A few caveats are worth knowing. Blur uses GPU acceleration, so on older Intel integrated graphics common in refurbished business laptops, it can reduce frame rates during video playback. Edge-tile can occasionally conflict with third-party tiling scripts, so enable it last if you use one. Both features are stable enough for daily use, but they are classed as experimental for a reason: a future elementary OS update may rename or remove them.

Customising window behaviour and keybindings

Gala inherits most of its keyboard handling from Mutter, which means the shortcuts people usually want to change live under org.gnome.desktop.wm.keybindings and org.gnome.mutter.keybindings. Australian users tend to remap a familiar set: Super+arrows for snapping rather than the default Pantheon scheme, Alt+Tab variants that include grouped windows, and a dedicated shortcut to bring up the workspace overview.

A useful pattern is to script your preferred layout and apply it as a small shell snippet kept in ~/.local/bin. You can override the window-tiling shortcuts with custom gsettings commands and then point a launcher at the script. This is the approach several Sydney-based elementary OS users describe in forum threads, because it keeps the changes visible and editable rather than buried in a settings dialog.

Mouse behaviour is configured through the org.gnome.desktop.wm.preferences schema. The focus-mode setting (click or sloppy) and the raise-on-click behaviour are the two most commonly adjusted. On multi-monitor setups, common in Australian home offices where a laptop docks into a vertical second screen, you may also want to tweak org.gnome.mutter edge-resistance and the per-monitor workspace behaviour so windows do not get stuck between displays.

If you rely on a non-US keyboard layout — and many Australians do, since AU keyboards add a third level to several keys — keep in mind that some default shortcuts use keys that sit in different physical positions on your layout. Test shortcuts after switching layouts, and bind to keysym names (like Super_L) rather than characters when you want layout-independent behaviour.

Tuning performance for everyday hardware

Australia's climate adds an interesting wrinkle to compositor tweaks. During December and January, when many parts of the country see days above 35°C, laptop thermals become a real constraint. A compositor that pushes the GPU hard will run hotter, and a thermally throttling CPU will make animations stutter rather than feel snappy. The connection is direct: a 200-millisecond animation on a cool machine feels smooth; the same animation on a hot one feels broken.

For users on older or budget hardware, the single best performance change is usually to reduce or disable animations entirely. Beyond that, vsync handling lives in org.gnome.mutter and can be tuned to trade latency for smoothness. Some integrated graphics drivers in Australia-sold laptops (especially older AMD and Intel chipsets) benefit from disabling the frame-clocking heuristic, which keeps a steadier frame time at the cost of slightly higher input latency.

You can verify the impact of your changes using a simple terminal test. Run glxgears (from the mesa-utils package) before and after a tweak to get a rough framerate indicator, or use gnome-system-monitor to watch CPU usage while resizing windows. The combination of these two checks is what most Australian users in the forums rely on before declaring a setting "good enough".

If you do encounter regressions, the cleanest rollback is the one mentioned earlier: keep a known-good dconf dump on disk and restore it with dconf load. Logging out and back in is usually enough to apply restored values without a full reboot.

Backing up, sharing and reverting your tweaks

Because so much of Gala's behaviour is stored in dconf, sharing a working configuration is straightforward. Running dconf dump /org/pantheon/desktop/gala/ > gala-backup.dconf produces a plain-text file containing every key and value under that path. You can include the Mutter experimental features and keybindings paths as well. The resulting file is small, human-readable, and easy to paste into a forum post or commit to a dotfiles repository.

This approach is exactly how many Australian elementary OS users collaborate. Someone in Adelaide might post their gala-backup.dconf on a community wiki, and a user in Ballarat can apply it with dconf load /org/pantheon/desktop/gala/ < gala-backup.dconf after a fresh install. It is far more reliable than describing changes verbally, and it survives point-release upgrades better than editing individual GUI tools.

If something goes wrong and you cannot remember which setting caused it, the nuclear option is dconf reset -f /org/pantheon/desktop/gala/, which returns every Gala key to its default. Pair it with the equivalent reset for /org/gnome/mutter/ and /org/gnome/desktop/wm/ to return to a known-clean state, then log out and back in.

A practical habit worth forming: after every tweak you decide to keep, append a one-line comment to your saved dconf dump explaining what it does and why you chose it. Six months later, when you are trying to remember why your window animations feel just right, that comment will be the most useful file on your system.