Is the Unlicense the same as public domain?

It is an attempt to place the work in the public domain, with a fallback licence for places where an author cannot do that. In the US it functions as a dedication. In some European jurisdictions moral rights cannot be waived, so the fallback does the work instead.

CC0 is longer, more carefully drafted, and more widely recognised by legal reviewers. The Unlicense is shorter and was written for code. If a corporate legal team will ever review your project, CC0 causes fewer questions. Neither grants a patent licence.

MIT requires the copyright notice to travel with copies. The Unlicense requires nothing. If you want attribution, use MIT. If you genuinely do not care what happens to the code, the Unlicense says so in plain terms.

Can I change my mind after using the Unlicense?

For future versions, yes. For copies already distributed, no. A dedication to the public domain is the most complete grant there is and there is nothing left to take back.

Does the Unlicense affect AI training on my code?

Not in a way that helps you. Public code under any licence has already been collected. The Unlicense simply removes the last formality. Licensing value sits in code that was never published, whatever licence text it carries.

The Unlicense: dedicating code to the public domain

The Unlicense is what you reach for when even MIT feels like too much paperwork. It is short, it is blunt, and it is the most complete grant a developer can make. That is also why it is worth understanding before using.

What the text says

Three moves, in a few paragraphs.

First, a dedication: anyone is free to copy, modify, publish, use, compile, sell, or distribute the software, for any purpose, commercial or not, by any means.

Second, the mechanism: in jurisdictions that recognise copyright, the author dedicates all interest in the software to the public domain, for the benefit of the public at large and to the detriment of their own heirs and successors. That phrase is in the text. It is meant to close every door.

Third, the fallback: the usual warranty disclaimer, plus a grant that applies where the dedication cannot. More on that below.

No attribution requirement. No notice to preserve. Nothing to include in copies.

Public domain versus permissive

The difference is what remains.

                      MIT                   Unlicense
                    ───                   ─────────
author keeps          copyright             nothing
user must             keep the notice       nothing
patent grant          no                    no
revocable             no                    no

Under MIT you remain the copyright holder and grant a very broad licence. The one thread back to you is the notice that has to travel with copies.

Under the Unlicense you attempt to stop being the copyright holder at all. There is no thread. Someone can take the code, remove every trace of you, and sell it, and that is precisely what you told them they could do.

For many people that is the point. Utility scripts, snippets, reference implementations, things you want to exist and never think about again. The Unlicense expresses that intent more honestly than MIT does.

Why the fallback clause exists

Not every jurisdiction lets an author abandon copyright. In parts of Europe, moral rights, the right to be identified and to object to derogatory treatment, are inalienable. You cannot give them away even if you want to.

So the Unlicense includes a fallback: where the dedication is not effective, the author grants an unconditional licence to do all the same things. The practical result is the same in every jurisdiction, reached by one of two routes.

CC0, the Creative Commons public domain dedication, uses the same structure with more careful drafting, which is why legal reviewers tend to prefer it. The Unlicense’s advantage is that it was written for code, is shorter, and is recognised by GitHub’s licence chooser.

┌─ WORTH CHECKING ─────────────────────────────────────────────────────┐
│                                                                      │
│  Private, finished, owned by you: $500+ each to AI labs.             │
│                                                                      │
│  [ See what my repos are worth ]                                     │
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

When to use it

When you want no obligations attached to the code at all, including attribution.

When the code is small enough that a licence longer than the code would be absurd.

When you are explicitly trying to prevent anyone, including you, from ever asserting rights over it.

When not to use it

When you want credit. Use MIT.

When patents could be involved. Neither the Unlicense nor MIT grants a patent licence. Apache 2.0 does, and is the safer permissive choice for anything substantial. See open source licenses compared.

When contributors are involved and you have not thought about their rights. A contributor’s code is theirs to dedicate, not yours, and a dedication you did not have the right to make is not a dedication.

When a corporate legal team will review the project. They will ask why you did not use CC0, and the honest answer is taste.

Irreversibility

Every licence on this site carries the same warning and the Unlicense carries it hardest. You cannot revoke a grant on copies already distributed. A public domain dedication is the most complete grant there is; there is nothing held back to reassert later. Choose it for code you are certain you never want back.

What it does to licensing value

Nothing, because there was none to affect.

Public code under any licence has been collected into training corpora already, and there is no market for what a buyer has. The Unlicense removes the last formality on top of that, which is tidy and changes nothing.

The code with licensing value left is the code that was never published, and that holds regardless of what licence text, if any, sits in its root. Why that is the case, and what it means for the repositories you never made public, is the argument of your MIT-licensed repo is worth nothing. What copyright actually covers, before any licence is applied to it, is in is code protected by copyright.

What is the Unlicense?