Who owns your website’s files, and would you get them if you asked?

The live site and the source files are two different things

Think of it like a printed menu. The menu on the table is the finished thing; the designer’s working file is what made it, and it is the only version anyone can edit cleanly. Websites work the same way.

• The published site: what visitors download. You can always save a copy of this from your own live site, and it is better than nothing.
• The source: the page templates, the stylesheet, the uncompressed photographs, the licensed fonts, the content in a form that can be re-laid-out, and the account settings that make forms and email work.
• The history: a record of what changed and when, which is what lets a new designer make one small fix without re-guessing the whole build.

A saved copy of the live pages is a photograph of your site. The source is the negative. Both are worth having; only one of them lets somebody else pick the work up.

What a real handover actually contains

If you asked today and someone handed you a genuine handover, this is what would be in it. Use it as a checklist, not to be difficult, but because it is much easier to collect while the relationship is current.

• Every page file and stylesheet the site is built from, in a folder you can copy anywhere.
• The original images at full size, not just the small versions squeezed for the web.
• The names of the fonts and who the licence belongs to, so the next person can stay legal.
• Your text in an editable form, so a rebuild does not start by retyping years of copy.
• A short written note of where the site is hosted, where the domain is registered, and which accounts send the contact-form email.
• Logins, or better, ownership transferred to your own email address on each account.

Two of those items are ownership questions rather than file questions, and they are the two that cause real damage when they are wrong. The domain in particular deserves its own five minutes: see who owns your domain, because a site you hold every file for is still stranded if the name pointing at it belongs to somebody else.

The pattern where the files genuinely cannot leave

There is a category of website tool, the all-in-one builders and some agency-owned platforms, where nobody is behaving badly and the files still cannot be handed over. The site is not a folder sitting somewhere; it is a set of rows in that company’s system, drawn as a page each time somebody visits. There is no folder to give you. Naming companies is beside the point, because the pattern is what matters and it repeats across many of them.

The honest version of that trade is fine: you rent a system that does a lot for you, and in exchange the site lives and dies inside it. The unpleasant version is discovering the trade only when you try to leave. So ask the question before you build, not after:

• If I stop paying, what do I keep?
• Can my content be exported in a form another designer can use?
• Can the design itself leave, or only the words?

Usually the answers are: the domain and the text can leave, the design cannot. That is worth knowing on day one. It also explains why a site that has to be rebuilt from scratch every time you switch suppliers quietly costs more over ten years than it looked like on the monthly invoice.

How to ask your current designer for a copy, without drama

Most designers will send you the files the same week. The request only lands badly when it sounds like the opening move in a dispute, so make it routine and give a reason that is about you, not about them.

Something like this is enough:

“Hi, doing some tidying up of the business records this month. Could you send me a copy of the site files and a short note of where things are hosted, so I have it on file? No changes needed, and nothing is wrong. Happy to pay for the time if it takes you more than a few minutes.”

Offering to pay for the half hour is what turns it from a challenge into an errand. Then put the copy somewhere that is not your laptop (a cloud drive, or a second hard disk), and repeat the request after any big change.

If nobody answers, you are in a different situation, and there is a checklist for it: what to do when your web designer disappears walks through recovering the domain, the files and the hosting in the order that matters.

The lines to check in a contract

You do not need a lawyer to read for these. Search the document for the words “own”, “licence”, “source” and “transfer”, and see what comes back.

• Who owns the finished work, and from when. Ownership on final payment is normal and fair. Ownership that never transfers is not.
• Licence or ownership. A licence to use a design is a rental with extra steps; you want the work itself, or at minimum a permanent licence with no ongoing fee.
• Source files named explicitly. “The website” is ambiguous. “All source files, images and content” is not.
• Handover on exit, included. If leaving triggers a fee, leaving is being discouraged.
• Accounts in your name. Domain, hosting and analytics registered to your email, not the supplier’s.

Here is our own position, written as something you can check rather than a promise: every Droom client gets the repository itself, the complete versioned site with its full change history, as the standard handover, delivered at launch rather than on request. The domain stays in the client’s name throughout, and there is no exit fee, because there is nothing to exit from. The pricing page states the same terms in writing, and the website service describes what the build itself includes.

If you take one thing from this page: the best day to ask for your files is a day when you have no reason to.