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 a printed menu. The one on the table is finished; only the designer’s working file can be edited cleanly.

• The published site: what visitors download. You can always save a copy from your live site, and it beats nothing.
• The source: templates, stylesheet, uncompressed photographs, licensed fonts, editable content, and the settings that make forms and email work.
• The history: what changed and when, so a new designer can make one fix without re-guessing the build.

A saved copy of the live pages is a photograph of your site. The source is the negative, and only the negative lets somebody else pick the work up.

What a real handover actually contains

Use this as a checklist. 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 web-squeezed versions.
• The font names and who holds the licence, so the next person stays legal.
• Your text in an editable form, so a rebuild does not start by retyping years of copy.
• A short note of where the site is hosted, where the domain is registered, and which accounts send the contact-form email.
• Logins, or better, ownership of each account moved to your own email address.

Two of those are ownership questions, and they do the real damage when wrong. The domain deserves its own five minutes: see who owns your domain. 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

With the all-in-one builders and some agency-owned platforms, nobody is behaving badly and the files still cannot be handed over. The site is rows in that company’s system, drawn as a page on each visit, so there is no folder to give you.

That trade is fine if you know it: you rent a system that does a lot, and the site lives and dies inside it. Ask before you build, not when you try to leave:

• 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 domain and the text can leave and the design cannot. A site rebuilt from scratch every time you switch suppliers costs more over ten years than the monthly invoice suggests.

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

Most designers send the files the same week. Make the request routine, with a reason about you rather than them:

“Hi, I’m tidying up 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, nothing is wrong. Happy to pay for the time if it takes more than a few minutes.”

Offering to pay turns a challenge into an errand. Keep the copy off your laptop (a cloud drive or a second disk), and ask again after any big change.

If nobody answers, follow what to do when your web designer disappears: the domain, the files and the hosting, in the order that matters.

The lines to check in a contract

No lawyer needed. Search the document for “own”, “licence”, “source” and “transfer”.

• Who owns the finished work, and from when. Ownership on final payment is normal. Ownership that never transfers is not.
• Licence or ownership. A licence to use a design is a rental; you want the work itself, or at least 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. A fee for leaving is there to discourage leaving.
• Accounts in your name. Domain, hosting and analytics on your email, not the supplier’s.

Our own position, as something you can check: every Droom client gets the repository itself, the complete versioned site with its full change history, delivered at launch rather than on request. The domain stays in the client’s name throughout, and there is no exit fee. The pricing page states the same terms, and the website service covers what the build includes.