MPEG-4 Visual

The MPEG-4 Visual standard, a widely used video compression format, has reached a significant milestone. As of July 19, 2026, all essential patents covering this standard have expired, making it patent-free. This development marks the end of a licensing program that was established in 2000 to manage the intellectual property rights associated with MPEG-4 Visual.

History of MPEG-4 Visual Patents

The MPEG-4 Visual Patent Portfolio License was introduced in 2000, covering essential patents from over 30 companies, including major industry players like Canon, LG, Microsoft, and Sony. These patents were crucial for the development and implementation of the MPEG-4 Part 2 Visual standard.

Over the years, these patents have been expiring, with most of them lapsing years ago. However, one patent, held by Siemens AG, remained active in Brazil until its expiration on July 19, 2026.

Implications of Patent Expiration

With the expiration of the last patent, the MPEG-4 Visual licensing program is effectively over. This means that companies no longer need to pay royalties for using the standard, which could lead to increased adoption and innovation in the field of video compression.

Key Patents and Their Expiration

Some notable patents that have expired include Siemens' European patent, EP 1,279,291, which lapsed in 2021, and US patents US 6,636,637 and US 7,068,721, which expired in 2018 and 2022, respectively.

Remaining Patents and Licensing

While the MPEG-4 Visual Patent Portfolio License has come to an end, it's essential to note that other essential patents may still exist outside of this program. Companies should still ensure they are compliant with any remaining patents and licensing requirements.

Future of MPEG-4 Visual

The expiration of patents related to MPEG-4 Visual is expected to have a positive impact on the industry, as it will reduce costs and barriers to entry for companies looking to develop and implement video compression technologies.

Technology teams are watching mpeg-4 visual closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.