AMD is changing the licensing model for Vivado, its FPGA design suite, in a way that removes free Linux access from future releases.
Starting with Vivado 2026.1, AMD’s new free Basic tier will be available for Windows only. Linux support will move to paid tiers, including Core and Pro subscriptions. AMD’s own licensing page says the new tiered model begins with the 2026.1 release and that Basic remains free with annual renewal, while reporting from Tom’s Hardware and Linux-focused outlets has highlighted that Linux is no longer included in that free tier.
That matters because Vivado is used to design and program AMD/Xilinx FPGAs: reconfigurable chips used in specialist systems where low latency, deterministic processing and high-throughput signal handling are important. In the media and entertainment world, FPGAs can sit inside broadcast infrastructure, real-time video processing hardware, capture and conversion devices, custom encoding pipelines, test systems and other specialist equipment.
The change is drawing criticism from Linux users because FPGA development is often tied to Linux-based engineering workflows, automated build systems and embedded development environments. Under the new model, developers who previously used no-cost Vivado releases on Linux may have to stay on older versions, move the free workflow to Windows, or pay for a Linux-compatible tier.
AMD has framed the Basic tier as intended for simple, entry-level use and has said that a large majority of Vivado users are on Windows. Critics argue that this does not address the central issue: Linux support still exists in the paid product, but is being removed from the free one.
For most production companies, this will not be a direct operational change. A broadcaster, post house or studio is unlikely to be opening Vivado as part of a normal production day. The impact is more likely to land on the engineering side of the supply chain: hardware developers, university labs, open-source FPGA projects, small vendors and technical teams prototyping video or broadcast systems.
The practical risk is ecosystem friction. If students, hobbyists and small engineering teams find AMD/Xilinx FPGA development harder or more expensive on Linux, some may stay on old toolchains or look more seriously at alternatives from other FPGA vendors. That does not immediately change what equipment a media company buys, but over time it can influence which platforms developers choose for new tools and products.
For media technology executives, the takeaway is narrow but useful: production infrastructure depends on deep technical toolchains that are mostly invisible until pricing or platform support changes. A licensing change in FPGA development software can ripple into the cost, pace and accessibility of the specialist hardware work that underpins parts of real-time video infrastructure.