We analyzed the End User License Agreements of ten major software companies — what each does well, the clauses worth borrowing, and the public controversies that reshaped them. Then use our free EULA generator to create one tailored to your software.
An End User License Agreement is the contract that lets someone use your software without owning it. When a user clicks "I Agree" during installation or first launch, they accept a license: a defined set of permissions (install, run, maybe mod) bounded by restrictions (no copying, no reverse engineering, no resale). You keep the intellectual property; they get the use.
A EULA is not the same document as Terms of Service. The EULA licenses the software copy; Terms of Service govern the ongoing service — accounts, acceptable use, uptime. Installed products with connected features (most games, most desktop apps with cloud sync) typically need both, and several companies below combine them into one hybrid agreement.
Descriptions summarize each agreement in our own words — follow the source links to read the current official text.
Operating Systems & App Store
★ The 'licensed, not sold' standard
Apple's software license agreements are the canonical example of the licensed-not-sold model: you buy a device or download an app, but the software itself remains Apple's property, licensed for use on Apple-branded hardware only. Apple also provides a default EULA that automatically covers every App Store app whose developer doesn't supply their own — a safety net worth knowing about, though it isn't tailored to any specific app's features.
Operating Systems & Productivity
★ License types and transfer rules made explicit
Microsoft's license terms are notable for distinguishing license channels — OEM (pre-installed), retail, and volume — each with different transfer and activation rights. The terms spell out exactly when a license may move to a new device and when it dies with the hardware. For any software vendor with multiple sales channels, this is the reference pattern for preventing license-transfer disputes.
Creative SaaS + Desktop Apps
★ Hybrid EULA/ToS for subscription software
Adobe shows how a modern EULA works when desktop software is sold as a subscription: the license to run Photoshop locally is conditioned on an active subscription, and lapses when payment stops. Adobe also reserves content-moderation rights over cloud-stored files — a clause that drew scrutiny in 2024 and illustrates why transparency about content access matters for user trust.
Game Distribution Platform
★ Digital purchases as subscriptions, said out loud
Valve's agreement is unusually candid: everything you 'buy' on Steam is a subscription to content, not ownership — a framing now surfaced at checkout following California's 2024 digital-goods disclosure law (AB 2426). Valve also dropped forced arbitration in 2024 in favor of courts, bucking the industry trend. Both moves show a EULA evolving under regulatory and litigation pressure.
Games & UGC Platform
★ Anti-cheat and user-generated content done thoroughly
Epic's EULA is a strong template for live-service games: it grants Epic a broad license to user-generated content (needed to operate creative modes), authorizes anti-cheat enforcement including hardware bans, and handles virtual currency with express no-refund, no-real-world-value terms. The structure cleanly separates what players own (nothing in-game) from what they're licensed to use.
Developer Tools / Game Engine
★ A cautionary tale about changing terms retroactively
Unity's 2023 'runtime fee' episode is the industry's clearest lesson in EULA change management: attempting to apply new fees to already-shipped games triggered a developer revolt, a public apology, a reversal, and eventually a commitment to let developers stay on the terms of the Unity version they shipped with. The current terms now include that version-lock promise — a trust mechanism other tool vendors have since copied.
Games & Modding Community
★ Plain-language drafting and community rules
The Minecraft EULA is famous for reading like a human wrote it — short summaries sit alongside the legal text. It threads a difficult needle: encouraging a massive modding and server community while barring commercial exploitation, with the 'one major rule' that you may not distribute modified versions of the game itself. Proof that a EULA can be enforceable and genuinely readable at once.
Media Streaming
★ Licensing content the provider doesn't own
Spotify's agreement handles a layered licensing problem: users get a limited license to the app and to stream content that Spotify itself only licenses from rights holders. Downloaded tracks stay playable only while the subscription is active. The termination and content-availability clauses make clear that catalog changes and feature removal are contractual rights, not breaches.
Communications Software
★ AI features and customer content, post-2023 lesson
Zoom's 2023 terms controversy — language that appeared to license customer meeting content for AI training — forced a rapid public clarification and a rewritten clause stating customer content is not used to train Zoom's or third parties' AI models without consent. For any product adding AI features, Zoom's revised drafting is the template for saying precisely what data does and does not feed models.
Design SaaS
★ Output licensing users can actually understand
Canva pairs its terms with a separate content license agreement answering the question every design-tool user has: what can I legally do with what I make? Free and Pro content carry different reuse rights, and the terms spell out where designs may be resold. Splitting product terms from output-licensing terms keeps each document focused — a good pattern for any tool whose users create sellable artifacts.
Enterprise Developer Tools
★ Why reading license changes matters
Java's licensing history is the enterprise cautionary tale: what was free under one agreement became chargeable for production use under another, and a 2023 shift to per-employee pricing changed costs again for many organizations. The lesson for EULA readers and writers alike: the license terms of your dependencies are business risks, and version-to-version license changes deserve the same scrutiny as code changes.
Exactly what the user may do: install on how many devices, personal or commercial use, perpetual or subscription-bound.
No copying, reverse engineering, decompiling, sublicensing, or resale — the clause that protects your code.
You keep ownership of the software; the user receives only the rights expressly granted.
Your right to patch, modify, or discontinue features, and whether updates are required to keep using the product.
What ends the license — breach, non-payment, piracy — and what the user must do afterward (uninstall, lose access).
Software is provided 'as is'; you don't promise it is bug-free or fit for a particular purpose.
Caps what you can owe if the software causes damage — often to the price paid.
Which jurisdiction's law applies and where disputes are resolved.
One-time purchase, subscription, freemium, per-seat? The license grant and termination clauses flow from this.
Reverse engineering, redistribution, cheating, commercial resale — be specific to your product's real risks.
If users create content in your product or AI features touch their data, state who owns what and what trains models (see Zoom's rewrite).
Don't copy another company's EULA — it's copyrighted and describes their product, not yours. Our EULA generator produces a draft specific to your software, platforms, and jurisdictions in minutes.
Clickwrap before first use, versioned copies in-app, and fresh acceptance on material changes — enforcement depends on it.
$500–$2,000+
per document
5–15 hours
of research & writing
Free
to get started
Every clause from this guide as a printable checklist — license grant to governing law — so nothing gets missed before launch.
A EULA (End User License Agreement) is a legal contract between a software provider and the person who installs or uses the software. Unlike a sale, a EULA grants the user a license — a limited right to use the software under specific conditions — while the provider keeps ownership of the code and intellectual property. EULAs typically cover the license scope, restrictions (copying, reverse engineering, resale), updates, termination, and liability limits.
A EULA licenses a copy of software the user installs or runs (desktop apps, mobile apps, games), focusing on intellectual-property rights and usage restrictions. Terms of Service govern the use of an ongoing service (websites, SaaS, online platforms), focusing on accounts, acceptable use, and the service relationship. Many modern products need both: a EULA for the installed client and Terms of Service for the connected account and cloud features.
Generally yes, if properly presented. Courts routinely enforce clickwrap EULAs, where the user must actively click 'I Agree' before installing or using the software. Browsewrap agreements — where terms are only linked somewhere without requiring assent — are much harder to enforce. To maximize enforceability: require affirmative acceptance before use, make the full text easily accessible, use readable language, and re-prompt acceptance when material terms change.
Yes. A EULA protects the developer regardless of price: it stops users from decompiling or redistributing your code, limits your liability if the software causes damage, and preserves your intellectual-property ownership. Free and freemium products arguably need EULAs more, because their large user bases increase both piracy and liability exposure. App stores also expect one — Apple applies a default Licensed Application EULA to iOS apps unless you provide your own.
The core clauses are: license grant (what the user may do), license restrictions (no copying, reverse engineering, or resale), intellectual-property ownership, updates and modifications, termination conditions, disclaimer of warranties, limitation of liability, user-generated content rights where relevant, data and privacy cross-references, and governing law. Games and platform products often add anti-cheat, virtual-goods, and community-conduct provisions.
No — for two reasons. Legally, a EULA is itself a copyrighted work, so copying one wholesale is infringement. Practically, a copied EULA describes someone else's product: wrong license model, wrong features, wrong jurisdictions, wrong liability posture. Courts can refuse to enforce terms that clearly do not match the actual product. Use examples to understand the structure, then generate or draft a EULA specific to your software.
Present the EULA where acceptance is unavoidable before use: during installation (desktop), on first launch (mobile and games), at account creation for connected products, and on your website for reference. App-store products should also fill the store's EULA field. Keep a dated, versioned copy accessible in-app — settings or about screens are standard — and require re-acceptance when you make material changes.
Review it whenever your product materially changes — new monetization (subscriptions, virtual goods), new platforms, user-generated content features, AI features that process user content, or expansion into new jurisdictions. At minimum, review annually. When you update, notify users and require fresh acceptance for material changes; quietly swapping terms undermines enforceability.
Create a EULA tailored to your software in minutes
Download a free, editable EULA template
Definition, enforceability, and key terms
Real T&C examples across industries
18 real-world disclaimer samples by type
How ChatGPT, Gemini & Claude handle privacy
Answer a few questions about your product and get a tailored End User License Agreement — license model, restrictions, platform requirements, and liability limits included.