Corel Software v. Microsoft: Court Rules for Defendant in Document Software Patent Case
What would you like to do next?
Choose your path based on your current needs:
📋 Case Summary
| Case Name | Corel Software, LLC v. Microsoft Corporation |
| Case Number | 2:15-cv-00528 (D. Utah) |
| Court | U.S. District Court for the District of Utah |
| Duration | Jul 2015 – Sep 2025 10 years 2 months |
| Outcome | Defendant Win – No Damages |
| Patents at Issue | |
| Accused Products | Word, Excel, PowerPoint, Outlook, OneNote, Publisher, Visio, Paint, and WordPad |
Case Overview
The Parties
⚖️ Plaintiff
An entity associated with Corel Corporation, historically known for productivity and graphics applications including WordPerfect and CorelDRAW. Active IP portfolio in software development.
🛡️ Defendant
One of the world’s largest technology companies. Its Office productivity suite generates billions in annual revenue and serves hundreds of millions of users globally.
The Patents at Issue
This landmark case involved three U.S. patents asserted against nine of Microsoft’s most commercially significant productivity applications:
- • U.S. Patent No. 8,700,996 B2 — directed to document interface and editing technologies
- • U.S. Patent No. 7,827,483 B2 — relating to document processing and display functionality
- • U.S. Patent No. 6,731,309 B1 — covering earlier-generation graphical or document rendering methods
Developing document software?
Check if your application’s design or functionality might infringe related patents.
The Verdict & Legal Analysis
Outcome
The U.S. District Court for the District of Utah entered final judgment **in favor of defendant Microsoft Corporation**. No damages were awarded to Corel Software, LLC, concluding a nearly decade-long dispute.
Key Legal Issues
A merits-based defense verdict in patent litigation typically arises from a finding of **non-infringement** (accused products do not practice asserted claims), **patent invalidity** (asserted claims fail to meet patentability requirements), or adverse **claim construction** rulings. Microsoft’s multi-firm defense team was well-positioned to pursue all these defensive vectors simultaneously.
Filing a software patent?
Learn from this case. Use AI to draft stronger claims that can withstand litigation.
Power Your Patent Strategy with Eureka IP
From novelty searches to patent drafting, Eureka’s AI-powered tools help you navigate the patent landscape with confidence.
⚠️ Freedom to Operate (FTO) Analysis
This case highlights critical IP risks in document software. Choose your next step:
📋 Understand This Case’s Impact
Learn about the specific risks and implications from this litigation.
- Analyze how major tech companies defend software patent litigation
- Understand defensive strategies against broad product assertions
- Review key claim construction outcomes in software patents
🔍 Check My Product’s Risk
Run a comprehensive FTO analysis for your own technology or product.
- Input your product description or technical features
- AI identifies potentially blocking patents
- Get actionable risk assessment report
High Risk Area
Broad software patent assertions
3 Patents Asserted
Against 9 Microsoft products
Defense Strategy
Multi-firm coordination proved effective
✅ Key Takeaways
For Patent Attorneys & Litigators
Merits-based defense verdicts in decade-long cases create durable claim construction records worth monitoring.
Search related case law →Multi-firm defense coordination is a proven model for high-stakes software patent defense.
Explore precedents →Broad product-scope assertions can complicate damages theories and invite more aggressive invalidity challenges.
Analyze claim strategy →For IP Professionals
Evaluate assertion portfolios against defendants’ litigation endurance, not just technical infringement strength.
Assess litigation risk →Parallel USPTO proceedings (IPR/PGR) likely extended this case’s timeline — factor this into case budgeting.
Estimate litigation costs →Defendant’s willingness to go to merits judgment signals a policy of non-settlement on contested software patents.
Understand defense tactics →For R&D Teams
Productivity software GUIs and document-processing workflows remain active areas of patent risk.
Start FTO analysis for my product →FTO analysis should specifically cover document interface and rendering patents before product launch.
Learn about FTO best practices →Competitor patent portfolios from legacy software companies warrant ongoing monitoring.
Try AI patent search →Ready to Strengthen Your Patent Strategy?
Join thousands of IP professionals using Eureka to conduct prior art searches, draft patents, and analyze competitive landscapes.