snvrkotics

W2FPL, version 1

Do what the fuck you want to, when you want to.

A public license for anything. It keeps the WTFPL's whole idea, total freedom in one line, and says out loud what the WTFPL leaves unsaid: that the freedom is worldwide, permanent and can't be taken back, and that the author isn't on the hook for what you do with it.

The terms, in full

  1. 0.You just DO WHAT THE FUCK YOU WANT TO, WHEN YOU WANT TO.
  2. 1.If the law where you are won't let the author give this up, the law can go fuck itself, and whether or not it ever does, the author gives you a free, worldwide, permanent, irrevocable license to do everything it allows, whenever the fuck you want to.
  3. 2.Know the right times to fuck, and fuck hard.
  4. 3.Ignore what the fuck I just said in step 2 because you have free fucking will.
  5. 4.This work comes as is, with no warranty of any fucking kind, and the author isn't liable for whatever the fuck happens when you use it.

Plus the preamble every copy carries: anyone may copy or change the license, as long as a changed version gets a new name. Full text.

Why it exists

The WTFPL is the shortest free license there is, and that's its charm. It's a real license, a grant of permission rather than a public-domain waiver, and the FSF lists it as free and GPL-compatible. What it never says is where the permission applies, for how long, or whether the author can take it back, and a permission given for nothing is the kind some lawyers worry can be revoked. Clause 1 settles that in the same terms CC0's fallback license uses: free, worldwide, permanent, irrevocable. The WTFPL also has no warranty disclaimer, which keeps some companies, Google among them, from letting staff contribute to work under it; clause 4 is that disclaimer. Clauses 2 and 3 are jokes, and clause 3 makes sure clause 2 never binds anyone.

How it compares

LicenseGrant stated as permanent and irrevocableDisclaimerConditions on you
WTFPL v2NoNoNone
WTFNMFPL v1NoLiabilityNone
CC0 1.0YesWarranty and liabilityNone
W2FPL v1YesWarranty and liabilityNone

Use it

  1. 1. Add the license and your notice. Save the plain text, unchanged, as LICENSE. The copyright line in it is the license's own; your copyright goes in a notice of your own, in a README or at the top of a file:

    Copyright (C) 2026 Your Name. Released under the W2FPL, version 1: https://snvrkotics.com/licenses/w2fpl
  2. 2. Tag it. Until it has an SPDX identifier, use the standard tag for licenses not on the list:

    SPDX-License-Identifier: LicenseRef-W2FPL-1.0
  3. 3. Link it. On the web, a license link tells search engines and Google Dataset Search what the work is under. Add the badge if you like:

    W2FPL<a href="https://snvrkotics.com/licenses/w2fpl" rel="license"><img src="https://snvrkotics.com/brand/licenses/w2fpl-badge.png" alt="W2FPL" width="88" height="31"></a>

    In schema.org data, set license to https://snvrkotics.com/licenses/w2fpl.

Who uses it

  • SNVRKOTICS Data, an open music metadata graph: every item, its JSON and the full dump.
  • dripgraph, a linked-data archive of what artists wear (the data, not the photos).

Using it somewhere? Email snvrk@snvrkotics.com and it goes on this list.

Propose a fucking idea

The W2FPL is written in public, and anyone can change what goes into the next version. Have an idea, a better joke, a hole in the wording? Open an issue on GitHub. Want to rewrite a clause yourself? Send a pull request against the text.

  • Get in, get credit. If your proposal makes it into a published version, you're a W2FPL coauthor: named below and in the repo, and covered by the license's own credit line, “and the W2FPL coauthors.”
  • Versions never change once published. Accepted changes go into the next version at its own URL, so nobody's license changes under them.
  • Proposals are W2FPL too. What you send is released under the W2FPL, so it can go into the license; you agree to that, and to being credited, when you submit.

Coauthors

None yet. The first accepted proposal puts your name here. Be the first.

For license list maintainers

Everything a reviewer at SPDX, the FSF or another license list needs, in one place:

Full name
DO WHAT THE FUCK YOU WANT TO, WHEN YOU WANT TO PUBLIC LICENSE
Proposed identifier
W2FPL-1.0
Version
1, October 2026
Author and steward
Caleb Gottfried, snvrk@snvrkotics.com, and the W2FPL coauthors
Development
In public at github.com/snvrk/w2fpl
Canonical text
https://snvrkotics.com/licenses/w2fpl (page), https://snvrkotics.com/licenses/w2fpl.txt (plain text)
Based on
WTFPL, version 2 (SPDX: WTFPL), renamed as its terms require
What differs
Clause 1, an explicit free, worldwide, permanent, irrevocable grant of everything the law allows (terms the WTFPL leaves unstated); clause 4, a no-warranty and no-liability disclaimer; clauses 2 and 3, non-binding (3 cancels 2)
Conditions
None: no attribution, notice, share-alike or field-of-use restriction
In use at
https://data.snvrkotics.com, https://dripgraph.com
Status
Not yet on the SPDX License List; not reviewed by the FSF or OSI

Questions

What can I use it for?

Anything you can copyright: software, data, writing, music, images, fonts. It was written for data first: SNVRKOTICS uses it for two open datasets.

Do people have to credit me?

No. Nobody has to credit you, keep your name on it, or tell you they used it. If you need credit, use a different license.

What does clause 1 actually do?

The WTFPL grants permission but never says it's worldwide, permanent or irrevocable. Clause 1 says exactly that, in the words CC0's fallback license uses: wherever the law won't let the author simply give the work away, you get a free, worldwide, permanent, irrevocable license to do everything the law allows.

Are clauses 2 and 3 conditions?

No. Clause 3 tells you to ignore clause 2, so nothing after clause 1 is a requirement. Using the work never depends on following them.

Can I combine W2FPL work with GPL or MIT work?

The W2FPL puts no conditions on you, so it shouldn't conflict with another license's terms. The FSF and OSI haven't reviewed it, so that's the author's reading, not a ruling.

Is it on the FSF's list?

Not yet. The FSF lists the WTFPL, which the W2FPL is based on, as a free and GPL-compatible license; the W2FPL itself hasn't been reviewed.

Does it disclaim warranty?

Yes. Clause 4: the work comes as is, with no warranty, and the author isn't liable for what happens when you use it. The WTFPL has no such clause, which is why some organizations, Google among them, won't let staff contribute to work under it.

Can I change the license?

Yes, as long as you change its name too. That's the same rule the WTFPL has, and it's how the W2FPL itself came to exist.

This page explains the license; it isn't legal advice.

Rights, royalties & links — free.Start free
The W2FPL: do what the fuck you want to, when you want to