How to Invoice as a 3D Artist: Rates, Terms and Templates

TL;DR: Structure 3D invoices around milestones (blockout, high-res, final delivery) with revision rounds defined, list render farm and software costs as pass-throughs, specify file formats and asset ownership, and invoice at each milestone sign-off rather than waiting until the full project ships.

Three-dimensional artists deliver models, textures, lookdev, animation, or real-time assets. Clients often scope poorly—your invoice should map to milestones (blockout → high-res → approved delivery) and revision rounds defined in writing.

Engine-specific deliverables (Unity, Unreal) deserve explicit filenames and formats on the bill or attached delivery sheet.

Studios rotate producers; when your invoice reads like a release checklist, the next person picking up the project knows what was already paid for and what is still open.

Typical rates

Hourly for R&D-heavy work; fixed milestones for game or product viz pipelines; day rates for studio embeds. Rendering farm costs as pass-through or marked-up—label clearly. Khronos glTF resources illustrate why standard formats reduce rework—external anchor when clients demand proprietary-only pipelines that slow you down.

Rigging and simulation are different skills—split lines when you provide both.

Lookdev iterations after approved concept art sometimes need separate caps—note overage rates on the invoice when rounds exceed the SOW.

Sample invoice line items

When to send the invoice

For milestone-based projects, invoice at each milestone sign-off: after blockout approval, after high-res model delivery, and after final files and formats are handed off. Do not advance to the next milestone until the current invoice is paid -- this protects both parties.

On hourly or day-rate studio embeds, invoice weekly or biweekly with a task summary pulled from your time tracker or project board. Include the ticket or task references so producers can cross-check.

For asset packs and library work (game props, architectural models), invoice 50% at kick-off and 50% on delivery. If the pack is large (20+ assets), add a mid-point progress draw to keep cash flow aligned with production.

Payment terms

Deposit (30%–50%) before heavy modeling; progress invoices per milestone; final on approval or Net 15 for reputable studios. Kill fees for canceled phases belong in contracts and partial invoices when triggered.

Purchase orders from big clients—reference PO number every time.

Indie teams may use smaller weekly slices instead of huge milestones—steady cash flow beats heroic crunch with one giant unpaid deliverable.

What to include

Project and asset list, milestone name, file format summary, hours if hourly, revision round number if billing overage, tax if applicable, total, due date. Use how to write an invoice for identifiers and numbering.

Link to delivery folder or version tag in memo for audit trails.

Pair with invoice must-haves when billing through vendor portals that reject PDFs missing tax IDs.

Common mistakes

Unlimited revisions for a flat—scope death spirals. Combined modeling and texturing when only one was approved—disputes. No definition of “final”—invoice against signed approval emails. Farm costs surprise clients—estimate early.

NDA prevents portfolio use—do not promise marketing usage on invoices.

Asset handoff without license line (“client owns final mesh per SOW”)—legal and finance interpret silence differently.

Lookdev references pulled from paid asset libraries need license pass-through or client-owned entitlements spelled out—otherwise someone assumes you indemnified every texture forever.

Template link

Our 3D artist invoice template fits milestones, hourly blocks, and expenses.

Reuse the same milestone names as your task tracker so producers can map invoices to boards in seconds.

Messy client CAD that needs cleanup before you can model deserves a “data prep” milestone or hourly discovery—otherwise you absorb engineering debt before the first pretty render.

FAQ

Should I charge for file-format conversions (FBX, glTF, USDZ)? If the SOW specifies the formats, include conversion in the milestone price. If the client requests additional formats after delivery, charge per format or per batch as a change order. Note each format on the invoice so the client's tech team knows exactly what was delivered and can verify compatibility.

How do I handle revision rounds that exceed the scope? Define included revision rounds per milestone in the contract (e.g., "2 rounds of revisions at each milestone"). Bill additional rounds at your hourly rate as a separate invoice line. Reference the SOW clause and the approval that triggered the extra work.

What if the client's concept art or reference changes mid-project? Issue a change order before reworking the asset. Show the original milestone scope and the new direction as separate line items on the invoice. This documents the pivot and prevents the client from expecting the rework at no additional cost.

Engine exports named in the SOW (USDZ, glTF, FBX) should match invoice line labels so approvers tie PDFs to tickets. Post-final lighting tweaks belong on a change-order bill—not unlimited free polish.

---

Join early access to bill 3D and CG projects with clearer milestones.