Why Is Overleaf Down? | Get Back To Editing

You open a project, and the editor stalls. The PDF pane spins. Or sign-in fails. When that hits near a deadline, it feels personal. It isn’t. Overleaf is a web app with several moving parts, and a break in one part can feel like “the whole site is down.”

This article helps you sort three buckets: (1) an Overleaf-side incident, (2) a browser or account issue, or (3) a network path problem between you and Overleaf. You’ll also get workarounds so you can keep writing while things settle.

What “Down” Can Mean On Overleaf

People say “down” for different symptoms. Name yours first.

• Site access fails: the page won’t load, or you get a blank screen.
• Projects open, but compile stalls: the editor loads, yet PDF build jobs never finish.
• Parts of the app fail: buttons don’t respond, file tree lags, or assets never load.
• One feature fails: Git sync, submissions, or add-ons break while editing still works.

Two Checks That Save Time

Check Overleaf Status First

If Overleaf is having a service incident, the quickest confirmation is their status site. Open Overleaf Status in a new tab and scan for any active notice.

If the status site shows an incident, skip local tinkering and use the workarounds later in this article. If the status site is clear, keep going. Many “down” moments are local to a network, device, or browser profile.

Try A Second Network Path

Switch paths, not settings. Test on mobile data, a hotspot, or a different Wi-Fi. If it works there, your first network is the suspect. If it fails everywhere, it leans toward an Overleaf-side incident or a broader routing issue.

Why Overleaf Goes Down During Deadline Hours

Planned Maintenance

Routine maintenance can cause slow loads, brief sign-in trouble, or short compile delays. Maintenance often shows up on the status site with a time window and affected components.

Backend Incidents

Unplanned issues happen: a dependency outage, a deploy problem, a queue backlog, or a storage hiccup. Upstream provider trouble can also knock services offline, as Overleaf has documented in a past post-mortem. The editor can load while compiles stall, or sign-in can work while project lists fail.

Traffic Spikes

Deadlines bring traffic bursts. Spikes can strain login, real-time sync, or compile capacity. You might see timeouts, delayed autosave, or PDF jobs that sit in line longer than usual.

Your Network Blocking A Required Host

Some networks block parts of Overleaf without blocking the main page. The editor may load, yet compile or PDF assets won’t. Managed networks can also block WebSocket traffic used for live editing.

DNS Problems

DNS tells your device where a domain lives. If a resolver is stale or misconfigured, you can get stuck on an old route, or a script host won’t resolve.

Browser Cache Or Extensions

Old cached scripts and aggressive blockers can break the editor UI. A single extension can block a file host, a cookie, or a request Overleaf needs for sign-in.

Why Is Overleaf Down? A Triage Flow

Run this flow in order. It keeps you from chasing ghosts.

Step 1: Can You Reach The Login Page?

Open Overleaf in a private window. If it won’t load, try a different browser. If it still won’t load, switch network path.

Step 2: Does The Dashboard Show Projects?

If you can sign in, see whether the dashboard shows your projects. A blank dashboard can point to a transient backend issue or blocked scripts.

Step 3: Separate Editor Load From Compile

Open a small project and click Recompile. If the editor is responsive but compile never finishes, the build queue may be backed up. If the editor itself freezes, it leans toward browser or network trouble.

Step 4: Test With A Tiny New Project

Create a minimal project and compile. If that works but one project fails, the issue may be project-specific. If even a tiny project won’t compile, it points to a service-side compile problem or a blocked compile host.

Fast Local Fixes That Often Work

Do one change at a time so you learn what fixed it.

Use Incognito, Then Disable Extensions

If a private window works, an extension or cached data is the likely cause. Disable extensions one by one, refresh, and retest.

Clear Site Data For Overleaf Only

Clear cookies and site data for Overleaf, then sign in again. This can fix stuck sessions or broken cached bundles.

Swap DNS On The Problem Network

If Overleaf works on mobile data but not on Wi-Fi, try a different DNS resolver on that Wi-Fi network. A stale resolver can send you to a bad route, or fail to resolve a script host the editor needs.

Check Proxy, VPN, And Security Apps

A proxy, VPN rule, or traffic inspection tool can break secure requests. A common pattern is: Overleaf works on a phone hotspot but not on office or campus Wi-Fi. Try turning off VPN and retry. If you manage the network, allow Overleaf domains and WebSocket traffic.

Symptom To Cause Map

Match what you see, then take the first move listed.

What You See	Likely Cause	First Move
Login page won’t load on any network	Service incident or broader routing issue	Check status site, then retry later
Login works on mobile data but not on Wi-Fi	Network filter, proxy, or DNS issue	Use hotspot; swap DNS if you can
Dashboard loads, project list is empty	Blocked scripts, cached bundle, or transient backend issue	Incognito test, then clear site data
Editor loads, PDF pane spins forever	Build queue backlog or blocked compile host	Try tiny project; switch network path
One project fails, others compile	Project-specific build problem	Clear generated files; retry compile
Buttons don’t respond	Extension conflict or cached scripts	Disable extensions; hard refresh
Disconnects while typing	WebSocket blocked or flaky Wi-Fi	Try hotspot; turn off VPN; retest
Git sync fails, editing works	Single component incident	Status site component check; retry later

Keep Working While You Wait

If Overleaf is offline, switch to “keep writing” mode.

Grab A Local Copy When You Can

If the dashboard loads even briefly, export the project as a ZIP. If you use Git sync, pull the repo too. Keep editing locally until the service is steady again.

Compile Locally When Online Compiles Stall

You can write in any editor and compile with a local TeX distribution. This is handy when the build queue is slow or unreachable.

Trim Heavy Builds

Comment out big figures, pause bibliography rebuilds, and compile only the section you need. Keep the full build for the final pass.

Project Problems That Mimic Outages

If other projects compile, yet one keeps failing, try these checks.

Runaway Builds

Loops, huge graphics, or repeated bibliography runs can make compiles crawl or time out. Temporarily remove the heavy part, then add it back in small steps.

Old Build Artifacts

Generated files can get in a bad state. Clearing them can fix weird errors that persist after you edit the source.

Make The Next Outage A Smaller Problem

You can’t prevent outages, but you can prevent panic.

Backup Routine

Pick one: Git sync, periodic ZIP exports, or a mirrored folder. Near deadlines, do it more often.

Minimal Compile Toggle

Add a switch that turns off heavy figures and slow steps. When compiles slow down, flip the switch and keep drafting.

Separate Writing Profile

Use a clean browser profile for Overleaf with few extensions. Put experimental blockers in a different profile.

Prevention Checklist

Habit	What It Protects	When To Do It
Pull via Git sync or export a ZIP	Local copy if access breaks	Daily; hourly near deadlines
Keep a “minimal compile” mode	Smoother drafting when builds slow	Set once; use as needed
Write with a low-extension browser profile	Fewer UI breaks from blockers	Always
Know a hotspot fallback	Bypasses office or campus filters	Before crunch time
Keep system clock correct	Fewer login token errors	Check monthly
Split large projects into smaller files	Easier error isolation	Early in the project
Store figures in the project	Less broken linking	During writing

Common Error Messages And What They Usually Mean

Error text can hint at where the break is. Treat it as a clue, not a verdict.

• 502 or 503: a gateway or service hiccup. This often matches an incident, a restart, or a traffic spike. Check the status site and retry after a short break.
• 504: a timeout. It can come from a slow network path, a proxy, or a backend queue that is not responding in time.
• 403: a block. On managed networks it can be a filter rule. It can also come from a stale session. Try incognito, then clear site data.
• Stuck on “Loading…” with no code: often a script or asset that never loads. Extensions and DNS issues are common causes.

If you can copy an error ID from the page, save it. It’s a short string that can help Overleaf trace the request on their side.

When To Reach Out

If the status site is green yet you still can’t work across multiple networks and devices, use Overleaf’s in-app contact options. Include a screenshot, the time it happened, your browser name and version, and whether it works on mobile data.