Linux Audio Development (LAD)

Mission

We aim to make Linux a first-class platform for professional music production by encouraging leading audio vendors to bring their software and plugins to Linux.

While Linux is the de facto standard operating system for synthesizers, keyboards, effect units and controllers, many established audio vendors still do not offer Linux versions of their products.

We want to showcase the advantages of Linux as an operating system for professional music production, help developers make or port and release their software for Linux, and, if possible, provide a platform for them to reach out for help. Ultimately, we want professional-grade audio software on Linux to become the norm, not the exception.

"We want the best audio software and plugins available natively on Linux."

Frequently Asked Questions

• What does producing music on Linux look like today?
  • () ()

    

    

    

  • The availability of both proprietary (Bitwig Studio, Mixbus, Reaper, Fender Studio Pro, Waveform, etc.) and Open Source (Ardour, Qtractor, Zrythm, etc.) digital audio workstations (DAW) and the flexible audio subsystem of modern Linux distributions, PipeWire, make Linux a serious alternative to macOS and Windows when it comes to computer-aided music production.
  • Beyond music production, the growing global emphasis on technological sovereignty and digital resilience is increasing the importance of Open Source software. And, as the world's leading Open Source desktop operating system, Linux is going to play an increasingly significant role across society.
  • Linux has come a long way and is now not only on a par with macOS and Windows in many areas, but even superior in some.
  • Of course, this does not mean that the experience of producing music with Linux is perfect. Especially when it comes to the range of available audio software and plugins, Linux still lags. And this even though it would be relatively easy for most audio vendors to compile and publish their audio software or plugins as native Linux versions, thanks to the widely adopted use of Open Source cross-platform frameworks such as JUCE.
  • And, yes, not all major digital audio workstations are available on Linux. For example, there is no Cubase, no Logic Pro (obviously), no Pro Tools, no Live (even though Ableton uses a Linux version of Live with their Push hardware), and no FL Studio for Linux.
  • The bottom line is that Linux is absolutely ready for music production. However, depending on which DAW, which audio interface or which audio software or plugins users want/need, they may have to make concessions or hope for an improvement of the market situation, which is what we're aiming for with our initiative.
• Why should I offer my audio software or plugins for Linux?
  • The Linux market is growing steadily, thanks in part to positive developments in the gaming sector (e.g. Steam Deck) and more and more audio vendors are offering their products for Linux.
  • The current status of the Linux user base could be compared with that of macOS a few years ago. The macOS user base was also relatively small at the time, but it grew rapidly over time and with it the range of software available for macOS. We expect a similar development for Linux.
  • So, the decision for an audio vendor to support Linux is currently still more of an ideological nature. But since the effort on their side is usually manageable, and the move to support Linux also has a sympathetic effect on their brand, we think it is already worth going that route today.
• How large is the target audience for paid Linux Audio software or plugins?
  • A growing number of professional Linux users are willing to pay for software, as seen in other industries such as video production.
  • As of August 2026, Linux enjoys a share of the global desktop computer market of around 10%.
• Should audio software or plugins for Linux be "Free and Open Source Software"?
  • audio software or plugins offered for Linux can be FOSS as well as proprietary and/or commercial.
  • Since Linux itself is so-called Free and Open Source Software (FOSS), one could assume that software distributed for Linux should also conform to this model. However, this is not the case.
• And what about Linux Audio hardware support?
  • A significant challenge for Linux-based music production lies in the limited availability of drivers and software support for audio interfaces and other hardware devices.
  • Fortunately, some manufacturers—such as RME or Focusrite—design their audio interfaces to be USB Class Compliant, allowing them to function on Linux systems without the need for drivers or additional software.
  • However, while certain devices can be fully operated through their onboard controls, others rely on companion software to configure specific functions. For some products, such as Focusrite's Clarett series, Open Source (FOSS) software alternatives are available to bridge this gap.
• Which audio vendors already offer their software for Linux?
  • There is a growing number of audio vendors who offer their products for Linux.
  • See our list of Linux Audio Developers or have a look at Linux DAW, an independent directory of music software for Linux.
• How can I copy-protect my audio software or plugins on Linux? What about services like iLok?
  • On Linux, similar to macOS or Windows, a variety of methods can be employed for integrating a copy protection mechanism into software. These include the use of generated serial numbers, keyfiles, watermarks, or server-based username/password pairs and challenge/response systems for login/authentication purposes.
  • iLok is not yet available for Linux, although PACE has announced plans to support Linux in the future, albeit without a specific release date. See Linux Support Request Tracking for up-to-date information.
• What do Linux users expect from audio vendors?
  • Linux users in general enjoy their freedom and usually do not want to be controlled or patronized by software vendors.
  • Invasive copy protection mechanisms and installers that do not transparently show users what is being installed where would most likely not be well received by typical Linux users.
  • Since many Linux users have advanced computer skills, they usually appreciate it when audio software vendors provide information about the build system used (e.g., distribution, libc/glibc version, etc.) for their software.
• What are the system requirements for a Linux Audio development computer?
  • As Linux generally has low hardware requirements and is often installed and operated successfully on older computers, the requirements for developing and compiling audio software or plugins for Linux are actually very low.
• What operating system should I use for development to maximize Linux compatibility?
  • Many Linux Audio developers use a stable, non-cutting-edge distribution such as Debian as their build system. This is to remain backward compatible with older versions of libc/glibc.
  • On cutting-edge distributions, it makes sense to use a container-based build system to compile the binaries against a non-cutting-edge libc/glibc version.
• What formats should I distribute Linux Audio plugins in?
  • On Linux, audio plugins are usually offered as VST3 and LV2, but also increasingly in CLAP format.
  • If your plugin is Open Source, providing build instructions is strongly recommended, allowing developers and advanced users to compile the plugin themselves.
• What formats should I distribute Linux Audio software in?
  • Flatpak should be considered the minimum distribution format, as it works across most Linux distributions and integrates with popular software center apps.
  • If your software is Open Source, providing build instructions is strongly recommended, allowing developers and advanced users to compile the software themselves.
• What are some best practices for file locations?
  • It is best to follow the XDG Base Directory Specification for anything that isn't a plugin binary, and use the standard, per-format directories for plugin binaries.
  • Configuration data: Use $XDG_CONFIG_HOME (which defaults to ~/.config) for settings, and configuration files (e.g., $XDG_CONFIG_HOME/vendor/app/config.ini).
  • User-generated content: Use $XDG_DATA_HOME (which defaults to ~/.local/share) for sound content, presets, etc. (e.g., $XDG_DATA_HOME/vendor/app/sample.wav).
  • Cache files: Use $XDG_CACHE_HOME (which defaults to ~/.cache) for caches, thumbnails, etc. (e.g., $XDG_CACHE_HOME/vendor/app/thumbnail.png).
  • Make sure to check whether the environment variables are actually set before falling back to the default locations, and namespace your files in vendor and app subdirectories (e.g., $XDG_CONFIG_HOME/vendor/app/files.ext) to avoid collisions with other software.
  • Plugin binaries: Install VST3 and CLAP plugin binaries into the standard per-format user directories, inside a vendor subdirectory.
    ~/.vst3/vendor/plugin.vst3
~/.clap/vendor/plugin.clap
  • LV2 plugins are the exception, their discovery mechanism scans bundles directly at the top level, so they should not be nested inside a vendor subdirectory:
    ~/.lv2/plugin.lv2

• With which DAWs and/or distributions should I test my Linux Audio software or plugins?
  • As with other platforms, testing audio software or plugins with different distributions and/or DAWs is also worthwhile on Linux.
  • The numerous Linux distributions and Desktop Environments or Window Managers can be an additional factor.
  • Many audio vendors test their audio software or plugins on Linux only to a limited extent, e.g. with Debian and Ardour.
  • However, an ideal scenario would be to test at least two distributions, e.g. an Arch Linux based distribution with KDE as the Desktop Environment and Debian with GNOME as the Desktop Environment.
• Do I need to worry about PipeWire (vs JACK or PulseAudio) or Wayland (vs X11)?
  • The short answer is no.
  • The long answer for PipeWire—Linux's modern, flexible audio processing engine—is that it was developed from the ground up to replace both PulseAudio and JACK in everyday use and does so seamlessly (and with no further ado) via pipewire-jack and pipewire-pulse. While most distributions have already switched to PipeWire as their default, only a few DAWs, such as Bitwig Studio, currently support PipeWire directly. Ultimately, however, this plays a minor role in everyday use, thanks to PipeWire's backwards compatibility.
  • The long answer for Wayland is a bit more complex. As Linux's modern display server protocol, Wayland was developed as a direct replacement for X11. Thanks to Xwayland, a compatibility layer for X11 integrated into Wayland, X11 audio software or plugins work without issues in most cases on Wayland. Additionally relevant for audio plugins in particular: none of the popular audio plugin frameworks currently support Wayland directly. However, this is actively being worked on for some frameworks, such as JUCE and DPF, and workarounds exist for certain scenarios. For now, this means that if a digital audio workstation (DAW) does not offer X11 support, it can't be run on X11. For example, Fender Studio Pro does not offer X11 support. However, such a DAW can load X11 audio plugins via Xwayland on Wayland without issue. The user won't even notice.
• Does Linux support high-resolution graphical user interfaces?
  • Yes, modern Linux Desktop Environments and Window Managers support high-resolution displays.
  • Just like macOS and Windows users, Linux users nowadays expect software to have graphical user interfaces that are sharp on high-resolution displays and that can be resized.
• What frameworks can I use to develop audio software or plugins for Linux?

  • Framework	License	Android	iOS/iPadOS	Linux	macOS	Windows	Cost
    DPF	ISC			✔	✔	✔	Free
    Dplug	Various (ISC, etc.)			✔	✔	✔	Free & Paid
    Faust	GPLv3 / proprietary	✔	✔	✔	✔	✔	Free & Paid
    HISE	GPLv3 / proprietary		✔	✔	✔	✔	Free & Paid
    iPlug	MIT			✔	✔	✔	Free
    JUCE	AGPLv3 / proprietary	✔	✔	✔	✔	✔	Free & Paid
    LV2	ISC			✔	✔	✔	Free
    truce	MIT / Apache 2.0			✔	✔	✔	Free
    VST3	MIT		✔	✔	✔	✔	Free & Paid

• What issues can block audio software or plugins from being ported or distributed on Linux?
  • There are certain circumstances in which it is difficult, if not impossible, to make audio software or plugins Linux compatible.
  • 1. If an audio plugin is dynamically linked and depends on external, system-wide, non-ABI libraries other than libc/glibc or libX11, it may not work. Like on other platforms, a plugin must not depend on external 3rd party shared libraries.
  • 2. If audio software or plugins use APIs that are not available on Linux, they will need to be replaced before porting.
  • 3. Using web views in an audio plugin could prevent it from running at all or result in it only being compatible with a very narrow subset of system configurations.
• Can I get help from experienced Linux Audio developers if I run into problems?
  • In the long run, we would like to mediate between experienced Linux Audio developers and such that are new to the topic, but unfortunately we are not there yet and currently can't offer any support in this regard.
• After all, can't Linux users just use Wine/yabridge to run Windows audio software or plugins?
  • With the help of libraries such as Wine or yabridge, Windows audio software or plugins can be used under Linux. However, this is sometimes associated with trial and error, involves performance losses and does not work with all Windows audio software or plugins.
  • There's a new generation of Linux Audio users who are not willing to accept a halfway functioning solution and only use native Linux software.

Developers Spotlight

These cards show a selection of audio developers who already offer their software or plugins for Linux. See all developers in the list version!

Interviews

• Alexander Chalikiopoulos (Wasted Audio)
• Andrea Scuderi (n-Track)
• Artemiy Pavlov (Sinevibes)
• baconpaul (Paul Walker)
• Bjørn Næsby (Sononym)
• Carlo Castellano (AudioThing)
• Chris Randall (Audio Damage)
• Christian Siedschlag (DDMF)
• Christopher Herb (Ternär Music Technology)
• Dan Korneff (Korneff Audio)
• David Schornsheim (u-he)
• David Viens (Plogue)
• Enrique Díaz (Audio Assault)
• Frederik Siepe (TheWaveWarden)
• Gergely Sövény (Intechstudio)
• Giorgio Presti (Signal Perspective)
• Guillaume Piolat (Auburn Sounds)
• (new) Jeff Mutschler (M Media Audio)
• Jeroen Jay Kerstens (The Him DSP)
• Mathieu Demange (Inphonik)
• Mike Start (Applied Computer Music Technologies)
• Oren (PolyVector) and Tara (Skunkie) (Punk Labs)
• Oskar Schachtschneider (Sinuslabs)
• Patrick Kunz (TAL Software)
• Roel Vugts (RV Audio Design)
• Samuel Gähwiler (Klangfreund)
• (new) Sebastian Kramer (Shy audio)
• Shane McFee (Kazrog)
• Stefano Zambon (Elk Audio)
• Steffen Langenfeld (Manda Audio)
• Vladimir Sadovnikov (Linux Studio Plugins)
• x42 (Robin Gareus)

Artists Spotlight

These cards show a selection of artists who use Linux for their productions. See all artists in the list version!

Interviews

• Alison Wilder
• Amadeus Paulussen
• Arend Lee Jessurun
• Audiojunkie (Sean Ercanbrack)
• Chris Mills
• G M Slater
• Morten Mosgaard
• Niels Ott
• Rhizome Industrie
• (new) Tor-Helge Skei
• Val Davis
• Venn Stone

How To Help

1. Use our Email Template to reach out to your favorite audio vendors and ask them for Linux support. 😎
2. Spread the word by using one of our ready-to-share Spotlight Interview Quotes!
3. Submit a working Hardware/Software Recipe to help others build their dream Linux Audio rig.
4. Make a Donation. 😇

Let audio vendors know that you are interested in native Linux versions of their software and plugins!

About

Linux Audio Development is an initiative by Amadeus Paulussen, with special thanks to:

• alf
• Christoph Strauss
• G M Slater
• Morten Mosgaard

as well as the fantastic and inspiring Linux Audio community around the world.

Contact

• Email (amadeus@linuxaudio.dev)
• Matrix (@amadeuspaulussen:matrix.org)
• Signal (@amadeuspaulussen.81)
• Mastodon (@linuxaudiodevelopment)
• PeerTube (@linuxaudiodevelopment

() Back to top