This is one of the more stressful situations in hiring freelance help, and it's common enough to be worth a real, practical answer rather than just sympathy. A developer who was responsive and reliable suddenly goes quiet, mid-project, with money already paid and work left unfinished. Here's what to actually do, in order.
First, Rule Out the Innocent Explanations
Before assuming the worst, a short gap in communication has a lot of ordinary explanations, a personal emergency, illness, a technical issue with their usual communication channel. A single missed check-in or a slower-than-usual response after one message isn't yet the crisis it might feel like. Give a reasonable window, a few days for a normal freelance relationship, before escalating your concern.
Send One Clear, Direct Message With a Real Deadline
Once the silence has genuinely gone past a reasonable window, send a single, clear message stating specifically what you need and by when. Not a vague "just checking in," a direct ask, a status update on the specific deliverable, by a specific date. This does two things, it gives a genuinely busy or overwhelmed developer a clear, easy way to re-engage, and it creates a real, documented record if the situation continues and you need it later.
Check Every Channel You Actually Have
If you originally connected through a platform, Fiverr, Upwork, a similar service, check messages there specifically, not just email or whatever channel became the default once the relationship was underway. Platform messaging sometimes surfaces things a personal inbox won't, and if this does escalate to a dispute, platform-based communication carries real weight in resolving it.
Understand What You're Actually Owed at This Point
This depends entirely on what was agreed and what's actually been delivered so far. If a project was paid in milestones, and only an early milestone was paid and completed, your position is different than if a large upfront payment was made against work that's now sitting unfinished. Review your original agreement, informal as it might have been, and get clear on what was actually promised, what's been delivered, and what payment has already changed hands.
Request Access to Whatever Work Exists, Even If Incomplete
Whatever code, designs, or content exists, even unfinished, is generally something you're entitled to, particularly for anything you've already paid for. Requesting access to a GitHub repository, a shared design file, whatever the actual deliverable format is, protects you regardless of how the relationship resolves from here, since it means the work isn't entirely lost even if this specific developer never returns to finish it.
Know Your Actual Recourse
If you hired through a platform: most freelance platforms have a formal dispute process, and payments made through the platform, particularly ones held in escrow until milestones are approved, offer real protection here. This is one of the strongest arguments for using a platform's payment system rather than paying directly outside it, even once a relationship feels established and trustworthy.
If you paid directly, outside a platform: your recourse depends on what was actually documented, an invoice, a written scope agreement, any contract. A payment processor dispute is sometimes possible depending on how payment was made, and for larger amounts, this may be worth a genuine legal consultation, though the cost and time of that route is worth weighing honestly against the amount actually at stake.
If a contract was signed: review it specifically for what it says about non-delivery, refunds, and ownership of incomplete work. A well-written contract addresses exactly this scenario, which is precisely why having one, even a simple one, matters more than it might seem to at the start of a project that appears to be going smoothly.
Finding Someone to Finish the Work
Once you've secured whatever exists of the current work, finding a new developer to complete it is usually more realistic than starting over, though it's worth being upfront with anyone new that you're picking up an abandoned project, since reviewing and understanding someone else's incomplete work honestly takes real time and should be priced accordingly, not treated as equivalent to a from-scratch quote.
How to Protect Yourself Going Forward, on This Project and the Next One
Use milestone-based payment tied to specific, verifiable deliverables, rather than large upfront payments against work that hasn't been proven yet, particularly early in a new working relationship before real trust has been established.
Keep all communication in writing, even informal, so there's a real record if something does go wrong later, rather than relying entirely on verbal or easily-lost conversation.
Get a real, even if simple, scope document and payment terms in writing before work begins, which is exactly the kind of upfront step that feels like unnecessary friction right up until the moment it's the only thing protecting you.
Watch for early warning signs, not just the eventual silence. A pattern of slow responses, vague updates, or shifting timelines before the actual silence starts is often a real, visible signal worth taking seriously earlier rather than waiting for it to escalate into a full disappearance.
Frequently Asked Questions
How long should I wait before assuming a developer has actually ghosted me?
A few days of silence after one direct, clear message with a specific deadline is a reasonable point to start taking the situation seriously. Waiting weeks in hope of a response, without escalating through whatever formal channels are available, usually just delays getting real resolution.
Can I get a refund if a freelance developer disappears mid-project?
It depends heavily on how payment was made and what was agreed. Platform-based payments held in escrow offer the clearest path to a refund for undelivered work. Direct payments outside a platform depend on payment method protections and whatever was documented in writing beforehand.
Should I leave a public review or warning about a developer who ghosted a project?
This is a personal decision, but an honest, factual account, focused on what actually happened rather than an emotional characterization, is generally more useful to other potential clients and more defensible if the review is ever disputed. Checking the specific platform's policies on reviews after a dispute is also worth doing before posting anything.
If you're dealing with an abandoned project right now and need someone to assess what exists and pick it up cleanly, I take on exactly this kind of work.
Get in touch: https://pixelanas.com/contact
Anas, full-stack Next.js developer building SaaS products and premium templates. X: @ASheikh69751