Ownership, in writing

Who Owns Custom WordPress Plugin Code: Copyright, Work for Hire and the GPL, in Plain English

You paid for the plugin. You may not own it. That sounds like a trick, and it is not one: under US copyright law, paying the invoice and holding the copyright are separate questions. This page explains why, using only what the Copyright Office, the US Code and WordPress.org publish. It is not legal advice.

November 13, 2026 · 9 min read

acmemovingco.com · plugin handover record
What the company holds for its booking plugin
Code, accounts and paperwork, each with an owner of record
Sample
Source repository and full historyAcme Moving Co. account
License stated in the plugin headerStated
Signed written agreement on ownershipOn file, reviewed by counsel
Hosting and domain accountsCompany email
CRM and payment API keysCompany accounts
Written guide for the next developerTwo pages
Illustrative: a sample handover record for a fictional moving company; not legal advice

The short answer

Paying a developer does not by itself make you the copyright owner of a custom WordPress plugin. Software is not one of the nine commissioned-work categories the US Copyright Office lists for work made for hire, and US law requires a transfer of copyright to be in writing and signed. WordPress.org says plugins inherit the GPL, while admitting a legal grey area. Ask your attorney.

On this page
  1. The freelancer is gone, and the code is still running checkout
  2. Work made for hire, as Circular 30 defines it
  3. The signed transfer that actually moves ownership
  4. Where the GPL fits, according to WordPress.org
  5. Questions to put to your attorney before anyone writes code
  6. Holding the keys, not just the paperwork
  7. When ownership is a reason to rethink the whole site

The freelancer is gone, and the code is still running checkout

A common story. A developer built the plugin that sends your leads to the CRM, or prices your shipping, or runs your booking. The invoice was paid. Three years later the developer has moved on, the plugin needs a change, and someone asks the question nobody asked at the start: whose code is this, legally?

Most owners assume the answer is theirs, because they paid. US copyright law does not work that way by default, and the gap matters when you want to hire someone new to change the code, sell the business, or stop a former developer from reselling what they built for you. This page lays out what the published sources say. Your attorney applies it to your contract. The Copyright Office itself says in Circular 30: "The Copyright Office cannot provide legal advice about the status of a work." Neither can we.

DataCram builds custom plugins, as the section overview describes. We state no contract terms here; ask any developer, us included, to show you the ownership language before work starts, and have your attorney read it.

Work made for hire, as Circular 30 defines it

The US Copyright Office's Circular 30, Works Made for Hire, revised August 2024, starts from a default: "Ordinarily, the author is the person or persons who actually created the work you intend to register. “Works made for hire” are an exception to this rule." When the exception applies, "the hiring or commissioning party is considered the author and the copyright owner."

The circular says a work is made for hire in two situations: when "created by an employee as part of the employee’s regular duties," or when "a certain type of work is created as a result of an express written agreement between the creator and a party specially ordering or commissioning it." For an outside studio, the first route is a poor fit: the circular's own questions for deciding employee status include whether "the creator have his or her own business" and how the creator was paid. So the second route is the one that matters, and it has conditions.

The four conditions Circular 30 (revised August 2024) sets for a commissioned work to be made for hire
ConditionWhat Circular 30 requiresWhere a plugin stands
A listed categoryThe work must fall in one of nine categories, such as "a contribution to a collective work," "a translation," "an instructional text" or "an atlas"Software is not named. Whether a plugin could fit a category is a legal question for your attorney
A written agreementAn express written agreement between creator and commissioning partyMany plugin jobs run on an email and an invoice
Express agreement on the statusThe parties must "expressly agree" the work "shall be considered a work made for hire"The phrase has to be in the document, not implied
Signatures"The agreement must be signed by all parties."Who signed, and how, is worth checking with your attorney

The consequence is spelled out: "If a work fails to satisfy any of these requirements, it is not a work made for hire." So a contract that simply calls a plugin "work for hire" may not settle ownership on its own. That is our reading of the circular, not legal advice.

Bright blue duotone of a person seen from behind holding a large key up to a tall door, framed by solid circles and rectangles in deeper blue
Paying for the plugin and holding its copyright are separate questions, settled on paper.

The signed transfer that actually moves ownership

If the work-for-hire route does not fit, ownership can still move from the developer to you. It moves by transfer, and the law is specific. 17 U.S.C. 204(a), as published by Cornell's Legal Information Institute and read in November 2026, says: "A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed or such owner's duly authorized agent."

Read that slowly. The statute asks for the signature of the owner of the rights conveyed, and Circular 30 says the author is ordinarily the person who actually created the work. A purchase order you signed does not do it. A paid invoice does not do it. Our inference from these sources, labeled as an inference: when an outside developer writes a plugin, your ownership of the code comes from a signed written transfer, not from paying the bill. Have your attorney review the wording.

The invoice proves you paid. Only a signed transfer proves you own.

Circular 30 also notes that even for works made for hire, the commissioning party is the initial owner "unless the employer or the commissioning party has signed a written agreement to the contrary with the work’s creator." Paper decides it at every turn.

Where the GPL fits, according to WordPress.org

Then there is the license WordPress itself uses. WordPress.org's license page, read in November 2026, says "The license under which the WordPress software is released is the GPLv2 (or later)" and "Derivatives of WordPress code inherit the GPL license." On plugins it states a position: "we feel strongly that plugins and themes are derivative work and thus inherit the GPL license."

That is WordPress.org's stated view, not a court ruling, and the same page admits as much: "There is some legal grey area regarding what is considered a derivative work." Its Plugin Handbook adds that "Most WordPress plugins are released under the GPL" and that "It is always best to clearly indicate the license your plugin uses." The plugin header has License and License URI fields for exactly that.

The directory has its own rules. WordPress.org's plugin guidelines say anything "stored in the plugin directory hosted on WordPress.org" must comply with the GPL or a compatible license. A private plugin built for one business and never submitted there is not in the directory, so by our inference that rule does not reach it. WordPress.org's broader derivative-work view is a different matter, and again one for counsel.

Questions to put to your attorney before anyone writes code

Bring these to the conversation with your attorney and the developer's draft agreement. They are questions, not answers.

  • Who owns the copyright when the work is done, and which signed document moves it, if a transfer is needed.
  • Does the agreement rely on work for hire alone, given that Circular 30 does not list software among the nine categories?
  • What about code the developer reuses from earlier projects or their own toolkit, and what license you get to it.
  • Which license the plugin header will state, and whether the plugin includes third-party code under its own license.
  • Who holds the repository, the hosting account and the API keys the plugin uses, and in whose name.
  • What happens if the developer stops working with you: what you receive, in what form, and how fast.
  • Whether the developer may reuse or resell the plugin, and whether that matters to you.

Our guide to hiring a plugin developer covers the rest of the interview, and the fair comparison of custom and off-the-shelf plugins covers when a bought plugin, with its own license terms, is the better deal.

Holding the keys, not just the paperwork

A signed transfer gives you rights. It does not give you the code. Owners who win the legal argument still lose months if the source sits in a former developer's private account. These are practical habits, not legal requirements.

  1. 1

    Put the repository in the company's name

    The code and its full history, in an account your business controls, with the developer added as a collaborator.

  2. 2

    Own the accounts the plugin needs

    Hosting, the domain, the CRM or field software API keys, any payment processor keys. Company email addresses, not a person's.

  3. 3

    Ask for a short written guide

    What the plugin does, where settings live, what it connects to. A new developer should be able to start in an afternoon.

  4. 4

    Keep a copy of the signed agreement with the code

    When you sell the business, the buyer's team will ask for both.

These habits are also what make plugin maintenance possible by anyone you choose later. If a plugin someone else wrote is broken today, our fixed-price plugin repairs run from $149 to $399, provided you can give us the code; the WordPress repair hub covers the wider site. The plugin security page covers what we check once we have it.

When ownership is a reason to rethink the whole site

Sometimes the ownership audit turns up more than one plugin. The theme, a page builder's saved layouts, three commercial plugins on lapsed licenses and a custom plugin nobody holds the source for. At that point the question is less who owns the code than whether the site is worth keeping. The free should I leave WordPress? check and our replacing WordPress service cover that road.

If you are staying, a new custom plugin starts at $575 to build, depending on complexity, with a fixed written estimate, as of November 2026; custom plugin development describes the work and the pricing guide explains what moves the number. DataCram is a web studio in San Antonio, Texas, building for the web since 1999, and our work shows what we have built. Start with a free site audit or call (210) 346-0848.

Questions owners ask about custom WordPress plugins

Not automatically. Under US law, a transfer of copyright ownership must be in writing and signed by the owner of the rights, under 17 U.S.C. 204(a). Paying the invoice does not by itself move the copyright. Check your signed agreement with your attorney to see what it says about ownership.

Not on a contract label alone. The Copyright Office's Circular 30 lists nine categories of commissioned work that can be made for hire with a signed written agreement, and software is not named among them. Whether a particular plugin could fit one is a legal question. Ask your attorney rather than relying on a contract label.

We do not answer GPL obligations here. WordPress.org's position is that plugins are derivative work and inherit the GPL, and the same page acknowledges a legal grey area about what counts as derivative. The GPL is also a separate question from who owns the copyright. Your attorney is the right person to ask.

It depends on who holds the copyright and what your agreement says about reuse and licensing. If the developer never signed a written transfer, they may still hold the copyright. Ask your attorney to read the agreement, and in future put reuse terms in writing before work starts.

Your attorney should draft or review it, but the questions are clear: who owns the copyright at the end, which signed document transfers it, what license applies to reused or third-party code, which license the plugin states, and who holds the repository and accounts. We state no contract terms here.

The directory guidelines govern plugins hosted on WordPress.org, and their license rule covers anything stored in that directory. A private plugin never submitted there is not in the directory, so by our inference those listing rules do not reach it. WordPress.org's general view that plugins inherit the GPL is a separate question for your attorney.

Keep reading

Free · No obligation

Sort out the code before you need it

Tell us what plugins the site depends on and who wrote them. Someone at DataCram replies with what we would need to take over, change or replace each one. Your attorney handles the contract.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote