Home / Guides / Upwork developer disappeared

Guide · Project rescue

Upwork Developer Disappeared? Do This Next

Your developer has gone quiet, the milestone is overdue, and you're staring at an unanswered message thread. Take a breath — this situation has a known playbook, and most of it is recoverable. This guide walks the steps in order: work out whether they've actually disappeared, secure everything you control, use Upwork's own process properly, get your assets back, and only then decide whether to wait, replace or rescue.

Skip to: secure what you control →App rescue service

In short

If your Upwork developer has stopped responding: first rule out timezone gaps and holidays (48 hours of silence is a delay; two weeks is a disappearance). Then secure what you control — change shared passwords, snapshot the repository, export data, screenshot the work history and chats. Keep all communication inside Upwork so there's a record, pause the contract, and open a dispute within the platform's window if money is held in escrow. Finally, take stock of what you actually have and decide: wait, hire a replacement freelancer, or bring in a rescue team. Everything below is the long version, in the order to do it.

This is practical guidance, not legal advice. For a valuable codebase or a large sum in dispute, speak to a solicitor.

Step 1 — before you do anything

Establish that they've actually disappeared

Don't accuse anyone yet. A surprising share of "my developer vanished" stories turn out to be a timezone mismatch, a national holiday, an illness, or a freelancer juggling too many contracts badly — unprofessional, maybe, but recoverable. Accusations made in hour 30 poison a relationship you might still need. Calibrate first:

Under 48 hours of silence: a delay, not a disappearance. Check the clock — a developer eight hours ahead of you answers your Friday-evening message on their Monday morning.
Check the calendar: public holidays in the developer's country, religious holidays, and any away or vacation notice on their Upwork profile.
3–7 days of silence on an active, paid contract: a genuine problem. Send one clear, unemotional message through Upwork asking for a status update by a specific date.
Two weeks with no reply anywhere: treat the engagement as over and work through the rest of this guide without waiting any longer.

Whatever the timeline, start the next step now. Securing what you control costs nothing, offends nobody, and loses all value if you leave it too late.

Step 2 — do this today

Secure everything you control, right now

This is the step people skip while they wait "a few more days" — and it's the one that determines how bad this gets. You are not accusing anyone by protecting your own accounts; you are doing basic hygiene that should arguably have been in place from day one.

If you have any access to the code — a repository invite, a zip they once sent, a server login — copy it somewhere you control before doing anything else. Repository access granted by someone else can be revoked at any moment.

The 60-minute lockdown

Snapshot the repo: clone or download the full repository (all branches) to your own machine and your own GitHub/GitLab account
Change shared passwords: hosting, domain registrar, databases, email, payment providers, app store accounts — anything they had credentials for
Rotate API keys and revoke OAuth grants or deploy keys tied to the developer
Export the exportable: database dumps, uploaded assets, environment configs, design files
Screenshot everything: the Upwork work history, milestones, payment records and the full message thread — dated evidence for any dispute

Don't lock the developer out of communication channels — you want them able to reply. Do make sure they can no longer be the only person holding the keys to anything you've paid for.

Step 3 — use the platform properly

Work Upwork's own process — it exists for exactly this

Credit where due: Upwork's escrow on fixed-price contracts is genuinely good buyer protection, and its dispute machinery is designed for the vanished-freelancer case. Use it in this order, and keep everything on the platform — off-platform emails and WhatsApp messages carry far less weight in a dispute than the official thread.

Message through Upwork, even if you normally talked elsewhere: one clear message stating what's outstanding, what you need, and a response deadline. This creates the record the process runs on.
Check the contract status: is a milestone funded in escrow and unapproved? Has anything been auto-approved while you weren't looking? Fixed-price milestones commonly approve automatically after a set review period if you take no action — so don't take no action.
Pause the contract so no further hours can be logged or milestones triggered while things are unclear.
Contact Upwork support and report the non-responsive freelancer; support can see things you can't and will note the case.
Open a dispute within the platform's window if money is at stake — unreleased escrow funds are generally recoverable when work wasn't delivered. Dispute and refund windows are limited and change from time to time, so check Upwork's current dispute process for the exact windows and steps rather than relying on any specific numbers you read elsewhere. (Process described generically; last verified July 2026.)

Stay factual and unemotional in everything you write on the platform — you're writing for the dispute reviewer as much as for the freelancer. And a note of realism: escrow protects unreleased funds. Money you've already approved and released for milestones is much harder to recover, and hourly contracts are judged on logged time, not outcomes. This is guidance, not legal advice; for large amounts, get proper advice on your options beyond the platform.

Step 4 — take stock

Recover your assets: the checklist

Whatever the dispute outcome, your project's future depends on what you physically hold. Go through this list and mark each item have it / can get it / gone — it becomes the briefing document for whoever finishes the build.

Asset	What to check	If you don't have it
Source code	Full repository with history and all branches, in an account you own	Request in writing via Upwork; check old email attachments, zips, CI systems and the server itself for deployable copies
Domain	Registered in your name, in your registrar account	If the developer registered it, ask for transfer in writing; registrars have dispute procedures if the domain is clearly your brand
Hosting & servers	Root/console access in your own account, billing in your name	Contact the host with proof of payment/ownership; snapshot or migrate the live app before anything gets suspended for non-payment
Database	A current dump you can restore, plus connection credentials	If you have server access, export it yourself today — data is the one thing a new team cannot rebuild
Credentials & keys	API keys, third-party service logins, app store accounts, signing keys	Rotate what you can, re-register what you can't; list every service the app talks to
Documentation	Specs, designs, README, deploy notes	Screenshot the live product thoroughly — it's the spec of record if nothing else exists

Once you know what you hold, the technical handover has its own playbook — see our guide to taking over another developer's code for how a new team audits and adopts a codebase safely.

Step 5 — the decision

Wait, replace, or rescue?

With your assets secured and the dispute in motion, you have three honest options — and the right one depends on the state of the code and how much runway you have left, not on how angry you are.

Wait — right if the developer resurfaced with a credible explanation, the work so far is good, and you've now fixed the structural problem (repo in your account, milestone billing, agreed response times). Give it one defined milestone to prove itself, not an open-ended second chance.
Replace — right if the project is in decent shape and simply lost its one developer. A vetted senior freelancer can pick up a clean, documented codebase; interview them against the asset checklist above and keep every account in your name this time.
Rescue — right if you're not sure what state the code is in, the product is partly broken, or deadlines mean you can't afford another single point of failure. This starts with an assessment of what exists, not a quote for a rebuild.

The deciding question is usually: can anyone but the missing developer actually run this project? If the answer is no — no docs, no tests, deployment knowledge in one absent head — a lone replacement inherits the same fragility. Our guide on how to finish an abandoned app walks through that assessment in detail, including when a partial rebuild beats a salvage.

Step 6 — if you need more than one pair of hands

When it's worth bringing in a team

Honestly: not every stalled project needs an agency. If what's left is a week of polish, hire a good freelancer and move on. A rescue team earns its cost when the problem is uncertainty — you don't know what's built, what works, or how long finishing will take, and you can't afford to find out by trial and error with another solo hire.

Our app rescue engagements typically start at £8,000–£12,000 (ex VAT): a structured audit of the codebase and infrastructure first, then a fixed, milestone-billed plan to finish — with the repository in your account, senior engineers you meet before committing, and a team on your timezone so questions get answered the same working day. Below that budget, we'll say so on the call and point you at the freelancer route instead — it's the right tool for smaller gaps.

What a rescue looks like

Audit first: what exists, what works, what's salvageable — in writing
Fixed plan, milestone billing: you pay against delivered stages, never far ahead
Your repo, your accounts: everything in your name from day one
Senior engineers you meet before you commit
Your working hours: hubs on UK, European and Gulf clocks

Questions & answers

Disappeared developer — FAQ

How long should I wait before treating an Upwork developer as disappeared?

As a rule of thumb: 48 hours of silence is a delay, not a disappearance — check timezones, public holidays in the developer's country and any away notice first. A week of silence on an active, paid contract with no explanation is a genuine problem. Two weeks with no reply through Upwork messages means you should assume the engagement is over and act accordingly: secure your assets, pause the contract, and start Upwork's dispute process if money is at stake.

Can I get my money back if my Upwork freelancer disappears?

Often, at least partially. Fixed-price contracts on Upwork use escrow: money for a milestone is held by the platform and only released when you approve the work, so unreleased escrow funds are generally recoverable through the platform's dispute process. Hourly contracts are harder, because payment follows logged hours. Timing matters — dispute windows are limited, so check Upwork's current dispute process for the exact deadlines and start early rather than waiting.

Do I own the code my disappeared developer already wrote?

Usually, for work you have paid for. Upwork's standard service terms typically transfer intellectual property in delivered work to the client once it is paid — but the terms in force and any custom agreement between you take precedence, so check Upwork's current terms and your contract, and take legal advice if the codebase is valuable. Practically, ownership only helps if you also hold the code, which is why snapshotting the repository is one of the first things to do.

What if I never had access to the repository at all?

Request it in writing through Upwork messages immediately, so there is a timestamped record. If the developer never responds, inventory what you do have — the deployed site or app, hosting account, database, and any files they sent — and work from that. A running application can often be substantially recovered even without the original repository. Then make repositories in your own account a non-negotiable condition of every future engagement.

Should I replace them with another freelancer or bring in a team?

Budget and the state of the project decide it. If the project was going well and simply lost its one developer, a carefully vetted senior freelancer can pick it up — keep the repository in your name this time. If the codebase is undocumented, partly broken or behind schedule, and your remaining budget is around £8,000–£12,000 or above, a rescue team is usually the better call: a paid assessment first, then a fixed plan with milestone billing.