Why Copyright and Source Files Belong in the Contract
A copyright without a source file is a lease. Write the rights line and the file line apart.
It is the day the sign shop needs the logo. The contract says copyright belongs to the client. The folder holds a web PNG. The owner thought they had bought the right. They had not bought a file they could change.
The last article bound acceptance and the last payment into one event. If what moves that day is only a screen, the bound event only half-closes. The rights sentence and the source sentence are not the same line.
This is not legal advice. It is the operations of writing the right and the file as two lines before you sign.
What “copyright transfers” does not close
The word vest calms people. Rights in a made work come in layers. Economic rights may be assigned in whole or in part. Unless a special term says otherwise, even a full assignment is read as leaving out the right to make and use a derivative work. Computer programs are the exception — that right is read as moving with the rest.(1) If the logo will grow onto a sign, a sticker, a film, the one word vest does not close that growth.
People who hire well do not write vest in a larger font. They split what moves from where it may be used. Some pieces, like a name credit, often stay with the maker. This article does not unwind that with a judgment. What operations can see is the belief that one word covers every later use.
If the work reworked another shop’s piece, the right in the base and the right in this job cannot share one line. If a font, a photo, and a track are mixed in, what can be assigned and what is only a license split. “All rights vest” hides that split. A hidden split is bought again later.
Assignment and a license are different sentences
Moving economic rights and allowing use are different acts. A licensee uses the work only in the method and conditions granted. Passing that permission to someone else needs consent again.(1)(2) Putting it on a site, printing it, and using it again in an ad are not the same grant if the conditions are empty.
People who hire well do not stack modifiers — exclusive, perpetual, every channel. They write where, how long, and in what form. A large-sounding license with empty conditions is an empty license. Empty conditions turn one more channel later into a new negotiation.
If it is an assignment, write assignment. If it stays a license, write license. Mix the two words on one line, and the owner reads owned while the shop reads lent. That mix is where a right without a source file begins.
Why the source file is a different line from the right
The right speaks to use. The source speaks to change. A psd, a Figma file, a repo are not rights papers. They are material you can open again. Move the right and leave the material, and you can use it and you cannot change it. If you cannot change it, you ask again for the next sign, the next season, the next owner of the work. A right you must ask to use is not a right you hold.
People who hire well park a file line under the rights line. They write what, in which tool version, on the handoff day. “All working files” cannot be counted. Write the extensions and the tool that opens them. For a repo, split access and a branch from a zip.
A screen export and a source are not the same folder. JPG and PDF sit near showing and print. A layered file, a file with components, a repo with commits — those are sources. If that split is missing from the contract, handoff ends as a screen export. A handoff that ends as a screen export cannot be told from a lease.
The state where you can use it and cannot change it
The site is open and you can edit a sentence. To change the layout you call the shop again. You can place the logo. To move a line you have no source. If this state looks like a dispute, it is late. It was set when the contract closed the right and left the file empty.
Even if the last payment and acceptance share a day, the event only half-closes if that day brings a screen export. People who hire well put the source on the acceptance list. If the source arrives late, they write — in the same bind as before — whether part of the last payment waits on that arrival or acceptance itself waits. “Please send it later as a favor” is not a line.
If the shop cannot give a source because of a tool license, write that limit now. Split the file they cannot give from the format they give instead. Leave only “rights vest” with the limit hidden, and the owner thinks they hold it while the shop has promised what they cannot hand over.
The two lines you write apart
The first line is the right. Assignment or license, which channels and term, whether growing a derivative is in. The second line is the file. Which source, when, with what access. If the two lines become one sentence, the rights word swallows the file. A swallowed file does not come back.
A Figma link can be open with view-only access. View-only is not a source. If a repo invite is pulled at the end of the project, commits existed and the handoff did not. People who hire well attach the kind of access and the day it may be pulled to the file line. A right sitting on pulled access is a lease again.
A license with no channel and no term sounds like “for our work.” Our work becomes an ad next year, and the ad becomes another pair of hands. If passing it to those hands sits outside the grant, you ask again. People who hire well split where you use it now from whether another pair of hands may take it. The rights line’s job is to cut the next time you have to ask.
A maker’s name credit sits on a different layer from economic rights. This article does not close that layer with a judgment. What operations can do is ask whether one line will keep the name. If you do not ask, credit later becomes a proxy war over the right. That war grows when the file line is empty.
Writing the two lines is not distrust of the shop. It is how the next owner of the work can open the same folder. A copyright without a source file is a lease.
The day the next owner cannot open the folder
The month the contact changes is the month the right is tested. The vest sentence remains. Figma opens only under the last person’s mail. People who hire well write the recipient of the handoff as a role — the operating account, not a name. A name leaves, and the folder leaves with them. A role lets the next person open the same door.
Some teams give back the tool seat when the hire ends. When the seat goes, the history of commits becomes a screenshot. A screenshot is not a source. People who hire well write, on the file line, the copy they will take before the seat is pulled. Asking after it is pulled is asking for a house whose lease already ended.
If another shop will edit the work later, ask now whether that pass sits inside the grant. If it sits outside, look at the assignment line again, or write a use range for the next shop. If you do not ask, the first week of the next hire starts with a rights check. A first week that starts as a check is rent charged by a right without a source.
This layer does not need the name of a judgment. It needs two questions: can the next person open the same folder, and may another pair of hands take it. Two lines that answer those questions let the work move even if the word vest is decoration. With no two lines, vest is comfort. A copyright without a source file is a lease.
참고
FAQ
Frequently asked questions
Is “copyright to the client” enough?
The one word vest does not close later use. Split assignment from license, and name the source.
Are assignment and a license different?
Yes. A license stays inside method and conditions. Passing it on needs consent again.
If we get the right and a JPG?
You can use it and you cannot change it. A copyright without a source is a lease.
Can we write “all working files”?
That cannot be counted. Write extensions and the tool that opens them.
Is this legal advice?
No. It is the operations of writing the right and the file apart.
Signs, stickers — growing the work?
Without a special term, even a full assignment is read as leaving that right out. Write the line if you will grow it.
If a tool license blocks the source?
Write that limit now. Split the file they cannot give from the format they give instead.
Related updates
What Belongs in a Dispute-Proof Contract
A vague line is not flexibility. Before you sign, edit the box that will mean two things later.
Read moreBlogHow to Write Deliverables and Revision Scope in One Line
If you cannot count it, it is not a deliverable. Not “a website” — five mains, eight subs, two draft rounds.
Read moreBlogWhen Acceptance and Final Payment Stay Vague
When acceptance and the last payment are different events, the files and the money come apart. Bind the three words to one day.
Read more