Free tools that run in your browser. Use any tool without an account.

Favourites Cart
Sign in
Join free

License Generator

  • Free
  • Runs in your browser
  • No account needed

This tool fills year and name for MIT, Apache-2.0, GPL-3.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and the Unlicense and returns a short summary plus the full official text. For example, make a 2026 MIT license for Acme Inc in seconds.

Runs in your browser. Your files and values are not sent to us. Report a problem
Advertisement

About the License Generator

This browser tool generates ready-to-copy LICENSE files for eight common open source licences: MIT, Apache-2.0, GPL-3.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and the Unlicense. You enter the copyright year and the holder name and the page fills the standard placeholders, shows a one-line plain-English summary, and displays the full canonical licence text. The tool runs entirely in your browser; nothing is uploaded or stored on a server. Developers, project maintainers and students use it to add a correct LICENSE file to a repo or release. Compared with many clones, this tool focuses on exact canonical texts and clear file headers so you copy the licence verbatim into your repository root or package metadata.

How to use it

  1. 1Select a licence from the list.
  2. 2Enter the copyright year and the copyright holder name.
  3. 3Click Generate to fill placeholders and show a short summary plus the full text.
  4. 4Copy the LICENSE text or download it to add at your repository root.
Advertisement

Worked example

Input: Licence = MIT, Year = 2026, Copyright holder = Acme Inc Output (exact): MIT License Copyright (c) 2026 Acme Inc 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.

How it works

Fills in the year and name for MIT, Apache-2.0, GPL-3.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and the Unlicense, with a short plain-English summary of each and the full official textWorks in the browser with nothing to install

Source: SPDX license listApache License 2.0 canonical textGNU GPL v3 canonical text. Last checked 5 November 2026.

What it is good for

  • Produces exact canonical texts you can paste into a repo.
  • Runs fully client-side so no files are uploaded.
  • Includes a short plain-English summary for quick choice.
  • This tool does not give legal advice and does not interpret licence terms.
  • It only fills placeholders and shows official texts for the listed licences.
Advertisement

Questions people ask

Which licences does this tool support?

It supports MIT, Apache-2.0, GPL-3.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and the Unlicense. Each output includes a one-line summary and the full canonical text.

Do I need to upload my repository or files?

No. The generator runs in your browser and does not upload files. You type the year and copyright holder and copy the generated LICENSE file into your repo.

Should I edit the licence text after generation?

You should not change the legal text of a licence. Replace only the allowed placeholders such as year and holder. For licence-specific headers follow SPDX guidance when adding source file comments.

Is the tool a substitute for legal advice?

No. The tool supplies canonical texts and summaries. For legal questions about compatibility, patent issues, or contributor agreements consult a lawyer.

Where should I put the generated LICENSE file?

Place a text file named LICENSE, LICENSE.txt or LICENSE.md at your repository root. Hosting services and package registries will detect it there.

What about SPDX identifiers?

The tool shows the common SPDX identifier (for example Apache-2.0 or MIT). You can add an SPDX-License-Identifier header to source files to make license scanning easier. See spdx.org for placement guidance.

Help keep every tool free

FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.

Advertisement
Advertisement