The full list of files to get from your web designer, not just the pretty ones
What counts as a complete file handover
Your new developer's first message asked you to "just send over the files," and you realized you had no idea what that meant. Most business owners picture a folder of pretty screenshots, maybe a logo file. That's not enough. Not close.
The phrase sounds simple. It isn't, and the gap between what it sounds like and what it should mean is exactly where a handover goes wrong.
A handover checklist you write yourself, before the first message goes out, closes that gap. It also gives the designer something concrete to work from instead of guessing what you meant.
Keep the checklist short enough to fit in a single email. A long, formal request can feel adversarial when a plain, itemized list gets the same result without the friction, and most designers respond well to a clear, specific ask.
A complete handover is closer to four separate things: the source files that built the site, a database export if the site is dynamic, the original image and asset files, and a full backup of the live site as it exists today. Sending only one of these isn't a handover. It's a partial one, and it will cost you later, usually at the worst possible time.
Ask for all four by name. Don't assume a general request will surface all four on its own. Write the list down before you ask, so nothing gets forgotten in the moment.
A developer switching projects has heard this request before. Naming all four items up front saves a second, more awkward email a week later.
Source files versus a live, running website
A live website you can browse is not the same asset as the source files behind it. The source is the actual working code — the templates, the scripts, the structure — in a form a new developer can open and build on directly.
Some designers will offer to keep hosting the live site "as is" instead of handing over source, which sounds convenient right up until you need to move it. At that point, a new developer is stuck rebuilding from what they can see on screen, which is slower and often more expensive than starting fresh would have been.
A screenshot is not source code. Neither is a page you can view but not open. If a developer can't download the underlying files, treat that as a gap worth closing now.
Ask specifically for a zip file of the site's directory, not just a description of what's in it. A working copy, not a summary, is the actual deliverable.
Database exports for dynamic sites
If the site runs on a CMS, a booking system, or anything that stores data — blog posts, product listings, form submissions — that data lives in a database, separate from the code that displays it.
A proper handover includes an export of that database, not just the code files sitting on top of it. Without it, a new developer is starting from a blank slate, even with every other file in hand.
Years of content can vanish in an instant if this one piece gets skipped. Ask specifically for it. Don't assume it's bundled in with everything else by default. A designer who built the site can usually generate this export in a single step.
Original image and asset files versus compressed web copies
The images on your live site have almost certainly been compressed and resized for the web. Those are not the same files a designer started with, and they were never meant to be the final word on quality.
Ask for the originals: full-resolution photos, layered design files, the actual fonts used, not just the web-optimized versions baked into the pages. You'll want them the first time you need a print flyer or a resized banner and discover the web copy pixelates the moment it's enlarged past a business card.
This one is easy to skip because nothing looks wrong on screen. It only shows up as a problem the first time you print. Keep a folder of originals separate from the working web files, labeled clearly, so nobody confuses the two later.
A clearly labeled folder, set up once, saves a frustrating search through years of website backups when a print job comes up unexpectedly, on a deadline, with a vendor waiting on the file.
Requesting a full backup even when you don't think you'll need it
Ask for a complete backup even if nothing is changing right now. Store it somewhere outside the designer's systems entirely — your own cloud storage, an external drive, anywhere you control directly. Do this once, and forget about it.
A backup is cheap insurance. It costs almost nothing to request and almost nothing to store, and it sits there quietly until the one day you need it.
Set a reminder to refresh the backup once a year, or after any major update to the site. A year-old backup is better than none, but a current one is worth far more.
Who owns your website is the underlying question these files answer; having them in hand is proof, not just a technicality. What to get in writing before you pay for a website covers how to put this request into the contract itself, so it isn't a favor you're asking for later.
Not every file can legally change hands. Template and theme licensing explains why some pieces of a site stay licensed no matter how complete the rest of the handover is. And if a relationship with a designer has already gone cold, what happens if your web designer disappears walks through what's still recoverable without their help.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go