How to get your website files when your developer has gone quiet

First, a fair word about the person who has gone quiet. Developers disappear for ordinary human reasons far more often than dishonest ones — illness, burnout, a business quietly failing, a solo operator who took on too much and cannot face the inbox. Some of these situations are recoverable with one patient email.

But you need your site either way. So: what to try, in order, including the part where the standard advice runs out — the moment you discover the accounts are not in your name.

First, check what you already control

People routinely have more access than they realize, because accounts were opened years ago and forgotten.

• Search your email for “welcome”, “your account”, “invoice”, the domain name itself, and the names of the big hosts and registrars. Welcome letters contain account numbers, and account numbers are what support desks ask for.
• Try a password reset at any registrar or host you find in those emails. If the reset email arrives at your address, the account is effectively yours.
• Try the site’s own login. For WordPress that is usually your domain followed by /wp-admin. A password reset there sometimes just works.
• Check your card and bank statements for recurring charges from hosting companies. A charge on your card is strong evidence of who is paying for what.
• Look up the domain in ICANN Lookup — the two-minute check tells you who the registrar is even when the registrant is somebody else, and the name servers usually identify the host.

Write down what you find. The list of what you do and do not control is the map for everything below.

Getting your files from the host

If you can get into the hosting account, this is straightforward. Most hosts provide a control panel with a backup or export function that will produce a full copy of the site files and the database. Download both. Store them somewhere that is not the server.

If you have WordPress admin access but not hosting access, a backup plugin will produce a complete archive from inside the site, which is enough to rebuild elsewhere.

If you have neither, this is where the standard advice sends you to the host — and where it gets harder, because a host will not hand over an account to somebody who asks nicely.

When you are not the account holder

Here is the escalation ladder, roughly in order of effort.

1. Ask once more, clearly and without heat

A short message that asks for a specific thing, states a date, and is easy to comply with: “Please send a full backup of the site files and database, and either transfer the domain to my registrar account or send the auth code. If it is easier, I can arrange the transfer myself.” A neutral note that costs the recipient ten minutes gets answered surprisingly often.

2. Build your proof of ownership

Hosts have account-recovery processes, and they hinge on evidence rather than on argument. Gather:

• Business registration documents in the name the account is likely under
• Card or bank statements showing you paid for the hosting or the domain
• Invoices from the developer that itemize hosting or domain registration
• The original welcome or setup emails, if any came to you
• Anything showing the business’s ownership of the trading name matching the domain

The single most valuable item is proof that your money paid for the account. That is the pivot most hosts use.

3. Open a formal account-recovery request with the host

Not a support ticket asking for help — a request that names the account, states your relationship to it, and attaches the documentation. Ask specifically what their process requires; most publish one, they vary, and they change. Be patient: these go to a different team than normal support and they are deliberately slow, because the same process protects you from somebody doing this to your account.

4. Ask the registrar about the domain separately

Domain and hosting are different companies and different processes. Registrars have their own dispute and recovery paths, and ICANN publishes guidance for registrants whose registrar will not resolve a complaint. Handle it as its own track rather than waiting for the hosting to be sorted out.

5. Recognize when it stops being a technical problem

If the accounts are genuinely in somebody else’s name, they will not cooperate, and the host cannot act on your documentation, then you are in a contractual dispute and the next useful conversation is with a lawyer rather than a support desk. That is not a defeat — it is the correct identification of the problem.

Two things not to do. Do not raise a chargeback as a lever: it can get the hosting account suspended, which takes your live site down and makes recovery harder. And do not attempt to guess or reset credentials on accounts that are not yours — whatever the moral case, it can turn a civil disagreement into something considerably worse.

What you are entitled to, and what you may not be

This is where people are most confident and most often wrong, so: this is not legal advice, and what follows is a list of things to check rather than a statement of your rights.

• Check your agreement for what was actually sold. A contract may transfer ownership of the finished work, or license it to you, or say nothing at all. All three are common.
• “I paid for it” is not automatically ownership. Depending on the arrangement and the jurisdiction, the person who created something may retain rights unless the agreement says otherwise. Worth checking rather than assuming in either direction.
• Content you supplied is a different question from code and design that somebody else produced.
• If there was no written agreement at all — common for small projects — then what happens next depends on facts and correspondence rather than on a document, which is exactly why a lawyer is the right person to ask.

The licensing trap

Almost nobody warns about this one, and it catches people who have successfully recovered everything else.

Premium themes and plugins are usually licensed to whoever bought them. If your developer bought a theme on their own license and used it on your site, that license does not transfer with the files. The site keeps working — but it stops receiving updates, including security updates, and you cannot get support for it.

So after recovering a site, check what commercial themes and plugins it uses and whose license each sits under. Buying your own licenses is usually inexpensive and it is far better than discovering the gap during a security incident.

Recovering content when you cannot recover the site

If the site is still online but you have no access, you can still get the content back:

• Copy it from the live pages. Tedious, effective, and it captures the text exactly.
• Right-click and save the images — although these are usually compressed versions rather than the originals, so retrieve originals from your own photographer or camera where you can.
• Use the Wayback Machine at archive.org if the site is already down. It has snapshots of a surprising number of small business sites, and it is the only free route to content that no longer exists anywhere else.

Text and images are the part that took real effort. The build is replaceable.

Before you rebuild, get the accounts right

If you are rebuilding, do this first, because it is the only moment when it is easy:

• Register the domain in your business’s name, at a registrar where you hold the login.
• Open the hosting account yourself, on your card.
• Then give whoever builds the site access to those accounts.

That order costs nothing extra and permanently ends this category of problem. The check that proves it worked takes two minutes.

So it never happens again

Ask any future supplier four questions: whose name the domain will be in, whose name the hosting will be in, what you take with you if you leave, and whether you can have a copy of the site on request. Then ask for that copy once, six months in, while everybody is still friendly. A supplier who provides it promptly has just proved the whole arrangement works.

Common questions

Who owns the website files, me or the developer?

It depends on your agreement, and this is not legal advice. Contracts variously transfer ownership, license the work, or say nothing. Content you supplied is a separate question from code and design somebody else produced.

Can a web developer hold my website hostage?

If the accounts are in their name they control access, which is why the registrant and billing details matter. Most cases resolve with a clear, unemotional request. Genuine refusals become a contractual matter rather than a technical one.

How do I get admin access to my own WordPress site?

Try a password reset at your domain followed by /wp-admin, using any email address that may have been used to set up your account. If that fails, access has to come through the hosting account, which means the host’s account-recovery process.

Can I get my website back if I have no logins at all?

Often, yes — but through the host and registrar rather than the developer. They act on evidence, so the useful first step is gathering business documents and statements showing your money paid for the accounts.

How do I download a backup of my website?

From the hosting control panel, which normally has a backup or export function covering files and database. With WordPress admin access but no hosting access, a backup plugin will produce a complete archive from inside the site.

Do premium themes and plugins transfer with the files?

Usually not. Licenses belong to whoever bought them, so a theme purchased on a developer’s license stops receiving updates on your site. Buying your own license is normally inexpensive and worth doing promptly.