Example License: Templates and How to Write Your Own

An example license is a template or sample agreement that defines how others can use your software, content, or intellectual property. Whether you are releasing open source code, selling a desktop application, or distributing creative works, having a well-structured license protects your rights and sets clear expectations for users.

This tutorial walks through real example licenses for common use cases and shows you how to write your own step by step. This content is educational and does not constitute legal advice. Consult a qualified attorney before finalizing any license agreement for your product.

What Is a License Agreement?

A license agreement is a legal contract between the rights holder (licensor) and the person or organization receiving permission to use the work (licensee). It defines what the licensee can and cannot do with the licensed material.

Under the Berne Convention (181 member countries), copyright protection is automatic. A license is the mechanism that grants others permission to use the work within defined boundaries. Every license agreement answers these core questions:

• What rights are granted? Use, modification, distribution, sublicensing, or some combination.
• What restrictions apply? Commercial use, attribution requirements, derivative works.
• Who owns the intellectual property? The license grants usage rights, not ownership.
• When does the license end? Perpetual, time-limited, or revocable under certain conditions.
• What law governs disputes? The jurisdiction whose courts handle any legal conflict.

Example License for Open Source Software

Open source licenses are the most widely available example license templates because their full text is published and standardized. Here are the most common ones with their key characteristics.

MIT License Example

The MIT License is the most popular open source license by adoption. Its full text is just 170 words:

MIT License

Copyright (c) [year] [copyright holder]

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

This example license allows commercial use, modification, and redistribution with only one requirement: include the copyright notice and license text.

Apache 2.0 License Example

The Apache 2.0 License adds two provisions beyond the MIT License: an explicit patent grant (contributors grant a royalty-free patent license for contributed code) and contribution documentation requirements (modified files must carry a notice stating they were changed). Google, Apache Software Foundation projects, and many enterprise tools use this license.

GPL v3 License Example

The GNU General Public License version 3 (GPL v3) is the most prominent copyleft license. Unlike permissive licenses, the GPL requires that any derivative work also be distributed under the GPL, ensuring improvements remain open source.

Key characteristics of this example license:

• Source code must be made available when distributing binaries
• Derivative works must use the same GPL v3 license
• Anti-tivoization clause prevents hardware restrictions on modified software

The GPL is used by Linux, WordPress, and thousands of other projects.

Example License for Proprietary Software

Proprietary software licenses are more restrictive and vary between vendors. Most follow a common structure.

End-User License Agreement (EULA) Template

A EULA is the standard license type for proprietary software. The key sections include:

1. License Grant

Define the scope of permitted use clearly:

• Single user or multi-user
• Number of devices or installations allowed
• Whether the license is perpetual or subscription-based
• Geographic restrictions, if any

2. Restrictions

Specify what users cannot do:

• No reverse engineering, decompilation, or disassembly
• No redistribution or sublicensing
• No use in competing products
• No removal of copyright notices or proprietary markings

3. Intellectual Property

State that the licensor retains all ownership rights. The license grants usage permission only, not a transfer of ownership.

4. Warranty Disclaimer

Most proprietary licenses provide the software "as is" without warranties. Some include a limited warranty period (30 to 90 days) covering defects in the installation media or basic functionality.

5. Limitation of Liability

Cap the licensor's maximum liability, typically at the amount the licensee paid for the license. Exclude liability for indirect, incidental, or consequential damages.

If you distribute software and need a EULA, tools like the TermsBox eula generator can help you create a structured agreement that covers these essential sections.

Example License for Creative Content

Content licenses govern how text, images, video, audio, and other creative works may be used. The most standardized examples come from the Creative Commons family.

Creative Commons License Examples

Creative Commons provides six standard license combinations built from four elements:

• BY (Attribution): Users must credit the creator
• SA (ShareAlike): Derivative works must use the same license
• NC (NonCommercial): Only non-commercial use is permitted
• ND (NoDerivatives): The work cannot be modified

These elements combine into six licenses ranging from CC BY (most permissive: use for anything with credit) to CC BY-NC-ND (most restrictive: non-commercial use only, no modifications, with credit). Choose the combination that matches how much control you want to retain over your work.

For custom content licenses outside the Creative Commons framework, follow the same structural principles covered in the proprietary software section: define the grant, restrictions, attribution requirements, territory, and termination conditions.

How to Write Your Own License Agreement

Writing a license agreement from scratch requires understanding your product, your users, and the legal framework that applies. Follow these steps to create a solid foundation.

Step 1: Define What You Are Licensing

Be specific about the licensed material. For software, identify the exact product name, version, and included components. For content, describe the specific works covered. Ambiguity in the subject matter of the license creates disputes.

Step 2: Choose Your License Model

Select the model that matches your business goals: perpetual (one-time payment, indefinite use), subscription (recurring payment with updates), freemium (basic free, premium paid), per-seat (price per user), or usage-based (price per consumption).

Step 3: Draft the Grant of Rights

Write a clear, affirmative statement of what the licensee is permitted to do. Use specific language like "Licensee may install and use the Software on up to three devices" rather than vague terms like "reasonable use."

Step 4: Define Restrictions

List everything the licensee is not allowed to do: reverse engineering, redistribution without consent, sublicensing to third parties, use in life-critical systems (if applicable), and removal of proprietary notices.

Step 5: Add Standard Legal Protections

Every example license should include a warranty disclaimer, limitation of liability (cap your maximum financial exposure), indemnification clause, governing law provision, and a severability clause ensuring the rest of the agreement survives if one clause is invalidated.

Step 6: Address Data and Privacy

If your software or service collects personal data, your license or associated privacy policy must address this. Under Article 13 of the GDPR, you must inform users about data collection at the point of collection. Under the CCPA (Section 1798.100), California consumers have the right to know what personal information is collected.

Your privacy policy should complement your license agreement by detailing what data you collect, how you use it, and what rights users have regarding their data.

Example License Mistakes to Avoid

Reviewing hundreds of license agreements reveals patterns of common errors that weaken enforceability or create unintended consequences.

• Overly broad grant of rights: Granting "all rights" or "unlimited use" when you mean something narrower strips your ability to control how your work is used.
• Missing termination clause: Without clear termination conditions, specify what triggers termination (non-payment, breach) and what happens afterward (cease use, destroy copies).
• Ignoring jurisdiction: A license without a governing law clause leaves dispute resolution uncertain. Choose a jurisdiction and state it explicitly.
• No version control: Failing to specify which software version is covered creates ambiguity. State whether the license covers one version or all future versions.
• Conflicting terms: If your license conflicts with your terms of service or privacy policy, courts may interpret the conflict against you. Review all legal documents together.

How License Agreements Interact with Other Legal Documents

A license agreement does not exist in isolation. It works alongside other legal documents that govern your relationship with users.

If your licensed product collects personal data, you need a privacy policy compliant with applicable regulations. The GDPR (Article 12-14) requires transparency about data processing, and the CCPA grants California residents specific rights over their personal information. Your license should reference your privacy policy and vice versa.

For SaaS products, the terms of service cover account management, acceptable use, and payment terms, while the license component addresses intellectual property rights. If your product provides information users might rely on for decisions, a separate disclaimer limits liability for outcomes beyond what the license warranty disclaimer covers.

Frequently Asked Questions

What should an example license agreement include?

An example license agreement should include a grant of rights defining what the user can do, restrictions on prohibited uses, intellectual property ownership clauses, warranty disclaimers, liability limitations, termination conditions, and governing law provisions. The specifics depend on whether you are licensing software, content, or a service.

Can I copy an example license and use it for my own product?

You can use an example license as a starting point, but you should customize it to match your specific product, business model, and jurisdiction. Standard open source licenses like MIT or Apache 2.0 can be adopted as-is. For proprietary software or SaaS products, a generic template may not address your specific needs for data handling, service levels, or usage restrictions. Consult an attorney for high-stakes licensing.

What is the difference between a license and a terms of service?

A license grants specific rights to use intellectual property such as software or content. Terms of service govern the broader relationship between a service provider and its users, covering topics like account creation, acceptable use, payment terms, and dispute resolution. Many SaaS products combine both into a single agreement, but they serve distinct legal functions.

Do I need a license if I distribute free software?

Yes. Without a license, default copyright law applies, which means no one has the right to use, modify, or distribute your code regardless of whether you charge for it. If you want others to use your free software, you must explicitly grant permission through a license. Popular choices for free software include the MIT License, BSD 2-Clause, and GPL v3.