1. Why Understanding License Types Matters

Every creative work — a photograph, a typeface, a piece of code, a piece of music — is automatically protected by copyright the moment it's created. That means no one else can legally copy, distribute, modify, or build upon it without explicit permission from the rights holder. Open licenses are the mechanism by which rights holders grant that permission to the public in advance, under specified conditions.

Understanding what those conditions actually say is essential for anyone who works with open assets professionally. The word "open" does not mean "do whatever you want." Some licenses require you to share modifications under identical terms. Some prohibit commercial use entirely. Some require patent grants. Some are designed specifically for fonts and prohibit selling the font file itself. Using an asset under the wrong assumptions about its license — or simply not reading the license at all — exposes individuals and businesses to real legal liability.

This guide maps out every major open license type clearly, compares their key terms side by side, and gives you a framework for making the right choice whether you're releasing your own work or evaluating something you want to use.

2. Two Categories: Content Licenses vs Software Licenses

Open licenses generally fall into two broad families, each designed for a different type of work:

  • Content licenses — Designed for creative works: images, music, videos, text, datasets, and other media. The Creative Commons suite is the dominant framework here, alongside platform-specific licenses like the Unsplash License.
  • Software licenses — Designed for source code, binaries, libraries, and by extension fonts (which are software files). These range from highly permissive (MIT, BSD) to strongly copyleft (GPL), with several intermediate options.

It matters which category a license belongs to because they address fundamentally different concerns. Software licenses deal with distribution of executable code, linking, patent rights, and binary vs source distribution. Content licenses deal with display rights, derivative works in a creative sense, and commercial monetization. Applying a software license to a photograph or a content license to a code library creates ambiguity and may not provide the protections either party expects.

3. Content Licenses

Creative Commons Family

Creative Commons (CC) licenses are the global standard for open content licensing. All CC licenses allow free distribution. What varies is the set of four optional elements that can be combined:

  • BY — Attribution required (applies to all CC licenses except CC0)
  • SA — ShareAlike: derivatives must use the same license
  • NC — NonCommercial: prohibits commercial use
  • ND — NoDerivatives: no modified versions may be distributed

CC0 (Public Domain Dedication) CC0 — The most permissive option. The creator waives all copyright and related rights globally. Users can copy, modify, distribute, and build upon the work for any purpose, commercial or not, without asking permission or providing attribution. Best for datasets, reference images, and work intended for maximum public benefit.

CC BY CC BY — Permits any use including commercial, with attribution required. The most permissive CC license that retains the attribution requirement. Used widely on Wikipedia (for text with certain exceptions), Flickr, and academic publications.

CC BY-SA CC BY-SA — Attribution required, and any derivative works must be released under the same CC BY-SA license. This is the "copyleft" of the Creative Commons world — it ensures that adaptations remain open. Wikipedia's text is licensed under a compatible Creative Commons Attribution-ShareAlike license.

CC BY-NC CC BY-NC — Attribution required, noncommercial use only. This is a popular choice for creators who want their work shared freely but don't want it used in advertising, sold, or incorporated into commercial products without a separate license negotiation.

CC BY-NC-SA CC BY-NC-SA — Attribution required, noncommercial only, and derivatives must share alike. The most restrictive of the sharable CC licenses. Often seen in educational resources and community art projects.

CC BY-ND CC BY-ND — Attribution required, but no derivatives allowed. The work can be shared in its original form for any purpose (including commercial), but no modified versions may be published. Useful for journalists, brands, and photographers who want their work circulated but not altered.

Important: NC and ND licenses are not considered "Free Cultural Works" by the Creative Commons organization itself or by the Open Definition. They place restrictions that limit creative freedom in ways the open source community generally considers non-free.

Unsplash License

The Unsplash License allows free use of photos for commercial and noncommercial purposes without attribution required. However, it explicitly prohibits selling unaltered copies of Unsplash photos as stock photos, compiling them into a competing service, or using them in ways that harm or misrepresent individuals. It is not a Creative Commons license and has no open version history — the terms are set by Unsplash alone and can change.

Pexels License

Pexels photos and videos are free to use for personal and commercial purposes without attribution, provided you don't sell unedited copies or use them in ways that harm Pexels or the depicted people. Like Unsplash, Pexels has its own proprietary license rather than a Creative Commons framework, which means you should always read the current license directly from their site rather than assuming CC0 equivalence.

4. Software & Font Licenses

MIT License

The MIT License is one of the most widely used open-source software licenses in existence. It is highly permissive: users can use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software. The only requirement is that the copyright notice and license text must be included in all copies or substantial portions of the software. There is no patent grant, no share-alike requirement, and no requirement to disclose source code. MIT-licensed code can be incorporated into proprietary commercial products freely.

Apache License 2.0

Apache 2.0 is similarly permissive to MIT, with two important additions. First, it includes an explicit patent grant — contributors to Apache-licensed projects grant users a royalty-free license to any patents they hold that are necessarily infringed by their contribution. Second, it includes a patent retaliation clause: if you sue any party for patent infringement related to the software, your patent license is automatically terminated. Apache 2.0 also requires that changes to the original files be documented. It is compatible with the GPL v3 but not with GPL v2.

GNU GPL v2 / v3

The GNU General Public License is the defining copyleft software license. The core principle: if you distribute a program that includes GPL-licensed code (or a modified version of it), your entire program must also be distributed under the GPL, with source code available. This "share-alike" requirement for software is called strong copyleft. GPL v3 adds explicit patent protection, anti-tivoization clauses (preventing hardware from blocking modified software), and addresses internationalization concerns. GPL v2 and v3 are explicitly incompatible with each other unless code is licensed "GPL v2 or later."

LGPL — Lesser GPL

The GNU Lesser General Public License allows non-GPL software to link to an LGPL library without the entire project being subject to GPL terms. If you modify the LGPL library itself, those modifications must remain LGPL. LGPL is used for libraries intended to be broadly adopted — the GNU C Library (glibc) and many Gtk+ components use LGPL. It strikes a balance between ensuring library improvements remain open while allowing commercial software to use the library.

Mozilla Public License (MPL 2.0)

The MPL takes a file-level copyleft approach. Code in MPL-licensed files must remain MPL-licensed if modified and distributed. But MPL code can be combined with proprietary code in a larger project — the proprietary files are not "infected" by the MPL, only the original MPL files and direct modifications to them. Firefox, Thunderbird, and LibreOffice use MPL 2.0. It is compatible with the GPL and LGPL.

SIL Open Font License (OFL 1.1)

The OFL is the standard open-source license for fonts. It allows fonts to be freely used, embedded, modified, and redistributed. Products that use the font — whether a website, a printed book, a software UI, or a logo — are not restricted. The restrictions are specifically on the font file itself: you may not sell the font file alone (it must be bundled with something else), and modified versions must be released under the OFL with a different name. The vast majority of Google Fonts are OFL-licensed.

BSD Licenses (2-Clause and 3-Clause)

BSD licenses are among the oldest open-source licenses. The 2-Clause BSD (also called the "Simplified BSD" or "FreeBSD" license) is essentially equivalent to MIT: retain the copyright notice, don't use the original author's name to endorse derivatives. The 3-Clause BSD adds a non-endorsement clause specifying that neither the project name nor the contributors' names may be used for promotional purposes without permission. BSD-licensed code is used in the core of macOS (Darwin), FreeBSD, and many networking components across the industry.

5. Full Comparison Table

License Type Commercial Use Modify Distribute Patent Grant Share-Alike Attribution
CC0 Content ✓ Yes ✓ Yes ✓ Yes ✗ No ✗ No ✗ Not required
CC BY Content ✓ Yes ✓ Yes ✓ Yes ✗ No ✗ No ✓ Required
CC BY-SA Content ✓ Yes ✓ Yes ✓ Yes ✗ No ✓ Yes ✓ Required
CC BY-NC Content ✗ No ✓ Yes ✓ Yes ✗ No ✗ No ✓ Required
MIT License Software ✓ Yes ✓ Yes ✓ Yes ✗ No ✗ No ✓ Notice only
Apache 2.0 Software ✓ Yes ✓ Yes ✓ Yes ✓ Yes ✗ No ✓ Notice only
GPL v3 Software ✓ Yes ✓ Yes ✓ Yes ✓ Yes ✓ Strong ✓ Required
LGPL Software ✓ Yes ✓ Yes ✓ Yes ✓ Yes ~ Library only ✓ Required
OFL 1.1 Font ✓ Yes ✓ Yes ~ With software ✗ No ✓ Font files ✓ Required
Unsplash License Content ✓ Yes ✓ Yes ~ Not as stock ✗ No ✗ No ✗ Not required

6. How to Choose the Right License

The right license depends on what type of work you're releasing, what freedoms you want to grant, and what obligations you want to impose on users. Work through these questions in order:

  1. What type of work is it? If it's source code, choose a software license (MIT, Apache, GPL, LGPL, MPL). If it's a font, choose OFL or Apache 2.0. If it's creative media (images, music, text), choose a Creative Commons license.
  2. Do you want to allow commercial use? If yes, avoid NC licenses. If you want maximum openness, choose CC0, CC BY, MIT, or Apache 2.0. If you want commercial use allowed but attribution required, choose CC BY or MIT.
  3. Do you want derivatives to remain open? If yes, choose a copyleft or share-alike license: CC BY-SA for content, GPL for software, OFL for fonts. If no, choose permissive licenses.
  4. Do you care about patent rights? If your project may involve patentable methods, Apache 2.0 or GPL v3 provide explicit patent grants and protection. MIT and BSD do not.
  5. Are you releasing a library for broad adoption? Consider LGPL or MPL 2.0, which allow commercial software to use your library without requiring the entire project to go open source.

Quick picks: For a personal project photo → CC BY. For open-source JavaScript → MIT. For a font you want to keep open → OFL. For a software library you want broadly used but protected → Apache 2.0. For a community-focused project where improvements must stay open → GPL v3.

7. Common Combinations & What They Mean for Projects

Real-world projects often combine assets under different licenses. Here's what to watch for in common scenarios:

  • MIT-licensed app using Apache 2.0 library: Compatible. Your app remains MIT-licensed, but must include the Apache 2.0 copyright notice for the library.
  • GPL v3 application using MIT-licensed component: Compatible. The MIT component is absorbed into your GPL v3 project; MIT's terms are more permissive and don't conflict.
  • GPL v2 and GPL v3: These two are not compatible unless both are licensed "or later." Never mix GPL v2-only code with GPL v3 code without resolving this first.
  • CC BY-SA content in a commercial publication: Allowed, but the publication itself must be released under CC BY-SA if it constitutes a derivative work. Many publishers avoid CC BY-SA for this reason and prefer CC BY or CC0.
  • OFL font used in a SaaS product: The OFL permits embedding the font in a web application and using it in a commercial service. Users see text rendered with the font — that's fine. The restriction is only on distributing the font file itself in ways that imply it's being sold as a standalone product.
  • NC-licensed image in a free blog with ads: This is a gray area. Many legal interpretations consider running advertising on a site to be commercial use, which would make a CC BY-NC license inapplicable. When in doubt, seek a CC0 or CC BY alternative.

8. Conclusion

Open licensing is not a monolith. Each license exists to solve a specific problem: ensuring attribution, maintaining software freedom, enabling broad commercial adoption, or protecting font designers from having their work sold without compensation. The best way to avoid legal risk is to treat license reading as a non-negotiable professional habit — not just a checkbox.

When in doubt, go more permissive for maximum reach, or more copyleft for maximum protection of openness. And always save a record of the license version and date you accessed it, since license terms can change between versions even under the same name.

Continue learning with our Commercial Use Checklist, the Creative Commons Explained article, and the Glossary for quick term lookups.