This page owns the software-specific patentability and prosecution question for European Patent Office. Filing deadlines, translations and formal national-phase requirements remain on the dedicated procedural page.
Software patentability under the EPC
Article 52 EPC excludes programs for computers from patentability only to the extent that the application relates to a computer program as such. The EPO Guidelines explain that a computer program can avoid the exclusion when it has technical character. For a program itself, that generally requires a further technical effect beyond the normal physical interactions between software and hardware. International applicants should therefore identify the technical purpose and implementation before drafting the first priority application.
Further technical effect should drive the disclosure
The EPO gives examples of further technical effects such as controlling a technical process or controlling the internal functioning of a computer or its interfaces. A specification should explain how the software changes a technical system, not merely what business or informational result it produces. Improvements in resource use, memory, processing, security, communications, image processing or machine control can be important when they are genuinely part of the invention and reflected in the claim.
Technical and non-technical features are assessed together
EPO examination of mixed inventions considers the claimed subject matter as a whole, but only features contributing to technical character can support inventive step under the established COMVIK approach. A business requirement can appear in the claim without itself creating inventive technical contribution. Software applicants should separate the non-technical objective from the technical means used to implement it and explain why those means are not obvious engineering choices.
Claims should include features essential to the technical effect
The 2026 EPO Guidelines state that claims directed to computer-implemented inventions should define the features essential for the technical effect of the process performed by the computer program. This creates a drafting discipline: if a technical effect depends on a particular architecture, data structure, processing step or device interaction, the claim should not omit that feature simply to become broader. Overly functional claims can create clarity and inventive-step problems.
Distributed computing requires special claim planning
The EPO Guidelines specifically address inventions implemented in distributed computing environments. Cloud, client-server and edge systems should disclose where each technical function occurs and how components interact. The application should support claims directed to individual devices, servers or subsystems where possible so that later enforcement does not depend on a combination of acts by separate entities.
Computer program, method, medium and device claims differ
EPO practice distinguishes a computer program from a computer-implemented method, computer-readable storage medium and device. A method involving technical means and technical devices themselves can have technical character, even though inventive step still requires a technical contribution. The specification should support the claim categories most commercially relevant to the applicant’s product and deployment model.
User interfaces and data processing need technical substance
A software invention focused on presentation of information, user interface or data organization can face difficulty if the claimed contribution is cognitive or informational. The application should identify whether the arrangement causes a technical effect, improves interaction with a technical system, controls a device or changes computer operation. A visually attractive interface or convenient information arrangement alone does not create the same patent position as a technical interaction.
Software and AI claims increasingly overlap
Many modern software systems incorporate machine learning. EPO AI guidance treats AI and machine learning as mathematical in nature as such, while allowing technical applications and implementations to contribute to patentability. A software filing should disclose the technical role of the model, the input-output relationship and any technical effect that depends on the AI component.
PCT regional phase strategy
Applicants entering the European regional phase should preserve claim support from the initial international application. New technical detail generally cannot be added later merely because EPO examination requires it. The PCT specification should therefore include the technical problem, technical effect, implementation alternatives and distributed architecture before the priority period closes. The dedicated EPO regional-phase page should be used for procedural deadlines and entry requirements.
Decision checklist for EPO software patents
Review the further technical effect, technical contribution, mixed technical and non-technical features, claim categories, essential technical features, distributed architecture, user-interface issues, AI overlap, inventive-step position, disclosure sufficiency and PCT support. The objective is not to describe software as technical in general terms, but to show exactly which claimed features create the technical result on which patentability depends.
Separate the durable technical contribution from product features
A software patent family should protect the technical mechanism that is expected to remain valuable as the product evolves. Interfaces, vendors, pricing models and deployment details can change faster than prosecution. The priority filing should therefore explain the engineering problem, the implemented solution, alternative embodiments and measurable technical effects with enough depth to support later jurisdiction-specific claims. This reduces the risk that the portfolio becomes obsolete because it was drafted around a temporary product configuration.
Design claims around identifiable commercial actors
International enforcement becomes harder when a claim requires unrelated users, cloud providers, manufacturers and platform operators to perform different steps. The specification should support claim positions focused on the actor that controls the technically important conduct where the invention permits. Server, device, system, process, component or product claims can create different evidence paths. The right architecture depends on the technology and the way competing implementations are expected to reach the market.
How to prioritize software claims for European Patent Office
A practical filing strategy should rank claim sets by commercial importance and enforcement value instead of treating every disclosed feature as equally important. The first layer should capture the technical function that differentiates the product. A second layer can protect narrower architectural details, data structures, security mechanisms, resource-management techniques or device interactions that may be easier to defend during examination. A third layer can address deployment-specific embodiments, such as server-side, client-side, edge or embedded implementations. This layered approach matters because prosecution can require amendment, and the original specification must already support those fallback positions. The goal is to preserve meaningful commercial scope while giving the examiner technically concrete alternatives.
Evidence of infringement should influence drafting
Software patents can lose practical value when the patented function occurs entirely inside a competitor's inaccessible backend. Before filing, the applicant should ask what evidence could show that the claimed steps are actually performed. Public API documentation, product behavior, network messages, device outputs, customer manuals, standards documents and observable system responses can all matter. Where an important feature is hidden, claims should, where the disclosure permits, include externally observable consequences or system relationships. This is separate from patentability, but it directly affects portfolio value. A technically valid patent that cannot be mapped to a competitor's product may provide less leverage than a narrower claim tied to observable operation.
