Should I charge by project or by hour as a freelance designer?

For most design work, project-based pricing wins. Clients want to know the cost upfront, and design rarely scales linearly with hours (a great logo might take 6 hours; a mediocre one might take 60). Use hourly pricing only for revisions outside the agreed scope, ad-hoc consulting, or truly open-ended work where neither party can scope deliverables in advance.

What are usage rights and how do I price them?

Usage rights define how, where, and for how long a client can use your work. By default in most jurisdictions you own the copyright; the client gets a licence. Pricing depends on use: a logo licensed only for a small local business is worth less than one for a global brand. For most freelance situations, a full transfer of rights upon final payment is simplest and is what most clients expect — document it on the invoice.

Should I deliver source files (PSD, AI, Figma) with the project?

This is your call, but the industry default is: deliver final assets in standard formats (PNG, SVG, PDF) by default, charge separately for editable source files. Many designers price source files at 25-50% of the project fee. Whatever you choose, write it down on the invoice so there is no ambiguity later.

What is a fair revision policy?

For most projects, two rounds of revisions per major deliverable is standard. State this in your contract and on the invoice. Bill any additional revisions as a separate line item at your hourly rate. This keeps revisions visible and chargeable rather than letting them quietly eat your margin.

What is a kill fee and when do I charge one?

A kill fee is what you charge if the client cancels the project mid-way. The standard structure is full payment for completed work up to the cancellation point at the agreed rate, plus a flat percentage (often 25-50%) of the remaining project value to compensate for the slot in your schedule that was already booked and is now unsellable. This belongs in the original contract, referenced from the invoice.

Do I need to include a copyright notice on my invoice?

Not strictly — copyright exists automatically the moment you create the work. But adding a short clause on the invoice like "Copyright remains with [your name] until full payment is received" is good practice. It makes the rights situation explicit and gives you leverage if payment is delayed or the client tries to use the work without paying.

Free Invoice Template for Freelance Designers — 2026 Guide

Designer invoices live or die on three things general invoices do not handle: usage rights, revision policies, and source files. A 2026 walkthrough with a free template.

Most freelance design contracts get clobbered at the invoicing stage — not because of the work, but because of language that is unclear about who owns what, when revisions are over, and what happens if the client cancels mid-project. Designer invoices live or die on three things general freelance invoices do not have to deal with: usage rights, revision policies, and source file delivery. Get those wrong and you have either lost money or signed away rights you did not mean to.

This is a 2026 guide to freelance design invoices — what to include, the line items that protect you, the language that matters, and a free template you can use in under 60 seconds.

Why design invoices need their own structure

A web developer’s invoice is mostly a list of hours. A copywriter’s invoice is mostly a list of deliverables. A designer’s invoice has to do something neither needs to: define a deal in plain language. When you hand a logo to a client, you are also handing them rights — to use it, modify it, sublicense it, or own it outright. The invoice (or its companion contract) is where those rights become enforceable.

This is not legalese for the sake of it. Designers who skip this step end up watching clients use their work in ways they never agreed to, with no recourse because nothing was written down. The good news is that the right language is short and reusable; you write it once, and every invoice afterward is faster.

12 things every freelance designer’s invoice must include

Below is the full structure. The first 8 are universal to any freelance invoice; items 9-12 are designer-specific.

1. Your business name and tax information

Top-left corner. Studio name (or your personal trading name), full address, email, and tax/VAT number if registered. If you operate under a personal name, use the same name that appears on the bank account that will receive payment.

2. The word "Invoice" and a unique invoice number

Use a sequential format: INV-001, INV-002 — never restart at 1, never skip numbers. If you bill multiple clients, prefix the invoice with a year (2026-001) or a short client code (ACME-001) for your own filing sanity.

3. Issue date and due date

Both dates, written unambiguously: "10 May 2026" — never "10/05/2026". Different countries read date formats differently; a US client may read 10/05 as October 5. The due date should be a specific calendar date, not a relative phrase like "Net 14".

4. Client name, contact, and billing address

Bill the legal entity, not your contact person. If your contact is "Sarah at Acme", the invoice goes to "Acme Inc., 123 Business St., …". For larger clients, ask which entity invoices should go to before sending; multinationals often invoice through a separate AP entity in their region.

5. Project name and reference / PO number

Designers tend to skip this and finance teams hate it. Every design invoice should include the project name in plain English ("Acme Brand Refresh — Phase 2") and any purchase-order or reference number the client uses. For mid-size clients, missing PO numbers are the single most common reason invoices get rejected and bounced back.

6. Itemised deliverables with descriptions, quantities, and rates

This is where designer invoices differ most from other freelance invoices. Resist the urge to bill "Logo design — €2,000". Break it out by deliverable so the client’s finance team can match line items to the work that was actually agreed:

Logo concept exploration (3 directions) — €600
Logo refinement (2 rounds, agreed) — €400
Final master logo (vector + PNG variants) — €600
Social media adaptation kit (10 sizes) — €400

Each line should be specific enough that someone who was not in the design meetings can map it to a deliverable in the brief.

7. Revisions billing as a separate line

One of the biggest mistakes designers make is letting revisions disappear into the project total. State the included revision count in your contract, and bill any extra revisions as their own line on the invoice — at your hourly rate, not a flat fee. This makes scope creep visible and chargeable instead of invisible and unpaid:

Additional revisions beyond agreed scope (4 hr × €80) — €320

8. Subtotal, taxes, and total due

Show the subtotal, then any applicable VAT/GST/sales tax as its own line, then the total due. If you are not VAT-registered, write "VAT not applicable" or "Tax: €0.00" rather than leaving the line off — finance teams sometimes flag missing tax lines for clarification.

9. Usage rights and licence terms

This is the line item that protects you. By default in most jurisdictions, the designer owns the copyright in their work even after delivery. The client gets a licence to use it, but they do not own it unless ownership is explicitly transferred — usually when full payment clears.

A short clause on the invoice (or a reference to your contract) like "Full usage rights and copyright transfer to Acme Inc. upon receipt of full payment. No rights granted prior" is enough to make this enforceable. Without it, ownership is ambiguous and leaves you exposed.

10. Source file delivery clause

Whether you deliver editable source files (PSD, AI, Figma, Sketch) is one of the most contested points in design freelancing. Best practice in 2026:

Final brand assets (PNG/SVG/PDF in the agreed colour profiles) are included by default
Source files (AI, FIG, layered PSD) are a separately invoiced line item, typically 25-50% of the project fee
State this on the invoice ("Source files: not included — available for additional €500 if requested")

This protects your future earnings (clients often come back for adjustments), without making you look like you are withholding the work.

11. Payment milestones for larger projects

For any project above roughly €2,000, milestones beat a single end-of-project invoice. Common structures:

50/50 — half on signing, half on delivery
33/33/33 — discovery, design, delivery
50/25/25 — protects you most when the project is open-ended

Each milestone is its own invoice, with its own number and due date. The first milestone invoice should clearly state the project total and which portion this invoice covers.

12. Late fees and kill fee clause

Two clauses every design invoice should reference. Late payment fee — typically 1.5-5% per month after the due date passes. Kill fee — what happens if the client cancels the project mid-way. Standard practice is that work completed up to the cancellation point is billable at the agreed rate, plus a flat fee (often 25-50% of the remaining project value) for the lost slot in your schedule. These belong in the original contract, not introduced for the first time on the invoice — but the invoice should reference them.

A worked example: branding project final invoice

Here is what a clean branding-project final invoice would look like, line by line:

Brand discovery workshop (3 hrs × €120) — €360
Logo concept exploration (3 directions) — €900
Logo refinement (2 rounds) — €600
Final master logo (vector + raster) — €600
Brand colour system (5 colours, accessibility-checked) — €300
Typography pairing — €200
Brand guidelines document (12 pages) — €1,200
Source files (AI + Figma) — €1,200
Subtotal — €5,360
VAT (20%) — €1,072
Total due — €6,432

Beneath the totals: "Full usage rights and copyright transfer to Acme Inc. upon receipt of full payment. Source files included as line item. Late payment fee 5% per month."

Common mistakes in designer invoices

Sending a single line item ("Branding — €5,000") with no breakdown
Using ambiguous date formats
No usage rights clause — leaves ownership undefined
Bundling source files into the project fee with no separate price
Vague revision count ("a few rounds") with no enforcement on extras
Hourly billing for project-shape work — clients prefer fixed deliverable prices
Missing kill fee — designer absorbs the loss when a project gets paused mid-flow
Sending invoice as Word document instead of PDF (many AP systems reject)