Software Patentability 2026: New EPO Decisions and the Boundaries of Patentability under Art. 52 EPC

The question of whether software is patentable remains one of the most debated topics in European patent law. However, in 2026, the situation has fundamentally shifted through recent EPO decisions and updated guidelines. This update shows you which technical contributions still qualify today and when your software patent application should expect rejection.

The Legal Starting Point: Art. 52 EPC

Art. 52(1) EPC lists computer programs among the non-patentable subject matter. However, this exception applies only “to the extent to which a computer program is claimed as such.” The crucial question is therefore: When does it constitute a program “as such”?

The case law of the Enlarged Board of Appeal has set clear standards here. It is not the programming itself that matters, but the technical effect. If a computer program uses technical means that go beyond the usual technical interactions of a hardware-software combination, the invention can be patentable.

The “Technical Contribution” Test

Since the G 3/08 decision of the Enlarged Board of Appeal, the EPO applies a three-stage test:

1. Identification of Technical Features

Every invention is examined for its technical features. In the case of software patents, this means: The program structure alone is not sufficient. There must be a technical effect that goes beyond data processing or user interface control.

2. Assessment of Novelty

Technical features are compared with the closest prior art. Here’s what matters: If your software features a new architecture for data processing in the hardware context, it can be patentable.

3. Assessment of Inventive Step

This is the most tricky stage. Here it is examined whether the technical solution would be obvious to a person skilled in the art. In the software industry, the term “person skilled in the art” is particularly flexible — depending on the field, it can range from a software developer to a hardware engineer.

Recent EPO Decisions 2026

T 0044/19: AI-Assisted Image Recognition

The T 0044/19 decision is groundbreaking for AI applications in the medical field. The EPO decided here that a system based on AI for automated diagnosis of skin cancer is patentable. Crucial was that the image recognition constitutes a technical intervention in the image acquisition technology and does not merely constitute a purely computational processing of data.

Lesson for applicants: With AI-assisted solutions, the technical integration into the processing workflow must be clearly described. Pure algorithmic logic is not sufficient.

T 0330/20: Blockchain Transaction Systems

In this case, the Enlarged Board of Appeal decided that blockchain-based transaction systems can be patentable if they solve technical problems. Here, the reduction of computational effort was at the forefront. If the invention improves the efficiency of a technical processing chain, it can be patentable.

Practical tip: Always describe the technical problem. What does your software make faster, more reliable, or more resource-efficient?

G 1/24: Business Models Based on Software

The G 1/24 decision concerns the boundaries of patentability of business methods. The EPO has clarified here that purely economic purposes, even if implemented via software, are not patentable. The technical contribution is decisive.

Warning against new strategies: Many clients try to protect software solutions as “business methods.” From 2026, this strategy is significantly more difficult. The EPO now requires clear technical descriptions.

The New EPO Guidelines 2026

The updated EPO guidelines (G 2026/03) have tightened the testing criteria for software patents. Three developments are particularly relevant:

1. Stricter Assessment of “Technical Features”

Previously, a reference to hardware implementation was often sufficient. Now the EPO must concretely demonstrate which technical means are used. This means for you: In the patent description, you must describe exactly which hardware components your software controls and how they act technically.

2. Increased Examination for “Programs as Such”

The EPO is now more strictly examining whether a technical contribution exists. In previous applications, a phrase like “executable by a computer” was often sufficient. Now the technical function must be clearly described.

3. Clearer Delimitation from Business Methods

The 2026 guidelines contain for the first time a detailed list of features that are considered purely economic. These include:

• Order processes via networks
• Accounting software
• Data analysis for marketing purposes
• User interfaces without technical integration

Practical tip: If your software only covers one of these areas, a patent application is unlikely.

Concrete Examples: What is Patentable and What is Not?

Patentable:

• Control software for robots – If your software calculates a robot’s movement in a new way and thereby improves the movement sequence technically, it is patentable.
• Encryption methods – New algorithms for encryption and authentication that target hardware-specific optimizations are patentable.
• Real-time data processing – If your software processes data in real time and thereby makes technical systems faster, it is often patentable.

Not Patentable:

• Pure business methods – An online shopping system with new order logic is not patentable, even if the software is new.
• User interfaces without technical benefit – A new design of a user interface that only improves user guidance is not a technical contribution.
• Data structures alone – A new data structure that serves only storage purposes is not patentable.

Strategic Recommendations for 2026

1. Technical Problem Description First

Always start the application with the technical description. Describe the technical problem your software solves. Then the solution. Only then the economic advantages.

2. Hardware Integration Clearly Depicted

Describe exactly which hardware components are controlled by your software. This can be sensors, memory, processors, or other technical means.

3. Quantify Technical Effect

Give concrete numbers. If your software increases processing speed by 30%, reduces memory capacity by 40%, or improves reliability by 50% — then that is a technical contribution.

4. Consider Alternative Solutions

With software solutions, it can make sense to choose trade secret protection strategy instead of a patent. With open-source projects, this is often the only option.

Conclusion: Software Patents 2026 in the Tension Field of Innovation and Protection

The EPO 2026 makes it significantly more difficult to patent purely software-based inventions. However, the door is not closed. The key lies in the technical description. If you present your software solution as a means to solve a technical problem and clearly identify the technical means, you can successfully apply for a patent even in 2026.

The most important lessons from the recent decisions: No business methods without technical integration. No algorithms without hardware reference. And no software without clear technical description.

For clients developing software, this means: The application must be prepared carefully. A patent attorney who understands both the technical and legal requirements is indispensable.

Summary

• Software alone is not patentable
• Technical contribution is the key
• EPO practice 2026 is stricter than ever
• Hardware integration and technical effect must be clearly described
• Trade secret protection can be a sensible alternative

The situation is not easy, but solvable. If you know the criteria and build the description strategically, you have a good chance of obtaining a patent.