Boneyard Tools

Open Source License Generator

Pick an open source license, fill in the copyright year and author, and get a ready-to-commit LICENSE file. Each option shows what it permits and requires so you can compare before you choose.

How to generate a LICENSE file

  1. Choose a license and read its permissions and conditions summary.
  2. Enter the copyright year and the author or organization name.
  3. Copy the generated text or download it as a file named LICENSE.

Examples

MIT license for Jane Doe

{ "type": "mit", "year": 2026, "author": "Jane Doe" }
MIT License

Copyright (c) 2026 Jane Doe

Permission is hereby granted, free of charge, to any person obtaining a copy...

Apache 2.0 notice

{ "type": "apache-2.0", "year": 2026, "author": "Acme Inc" }
Copyright 2026 Acme Inc

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License...

Frequently asked questions

Which license should I pick?

This page summarizes what each license permits and requires, but it is not legal advice. MIT, BSD and ISC are simple and permissive; Apache 2.0 adds a patent grant; GPL 3.0 is strong copyleft; MPL 2.0 is file-level copyleft; Unlicense is public domain. For anything important, ask a lawyer.

What is the difference between permissive and copyleft licenses?

Permissive licenses (MIT, BSD, ISC, Apache 2.0) let others reuse your code in closed-source projects as long as they keep the notice. Copyleft licenses (GPL 3.0, and MPL 2.0 at the file level) require that derivative works stay open under the same terms.

Why is the Apache, GPL or MPL output only a notice block?

Those licenses are long and must be reproduced verbatim, so their official policy is to put a short notice in your project and ship the full license text alongside it. The generator outputs the exact standard notice and links to the canonical full text to append.

Where do I put the file and what do I name it?

Save it in the root of your repository as a file named LICENSE (no extension). GitHub, npm and most tools detect that name automatically. For GPL you may also see it named COPYING; either works.

Can I change the license later?

You can relicense future versions if you hold the copyright or have permission from all contributors, but you cannot revoke the license already granted on code people have received. Adding contributors makes relicensing harder, so choose early.

Is anything I type sent to a server?

No. The license texts are built into the page and the file is generated entirely in your browser. Your year and author name never leave your device.

Related tools