507 Insufficient Storage

What HTTP 507 Insufficient Storage Means

The server cannot store the representation needed to complete the request.

A WebDAV status meaning the server has run out of storage (disk, quota) required to save the resource.

Common Causes

• Disk full on the server
• WebDAV user quota exceeded
• Temp/upload directory out of space

How to Fix It (For Visitors)

• Try again later
• Contact the site administrator

How to Fix It (For Developers/Admins)

• Free disk space or expand storage
• Raise the user/quota limit
• Add monitoring and alerts for disk usage

Returning a 507 Insufficient Storage (Code Examples)

If you build APIs or web apps, here is how to send an HTTP 507 response and how to test for it:

Node.js (Express)

app.get('/resource', (req, res) => {
  res.status(507).json({ error: 'Insufficient Storage' });
});

Python (Flask)

@app.route('/resource')
def resource():
    return jsonify(error='Insufficient Storage'), 507

PHP

<?php
http_response_code(507);
header('Content-Type: application/json');
echo json_encode(['error' => 'Insufficient Storage']);

Check the status with curl

curl -I https://example.com/resource
# Look for: HTTP/1.1 507 Insufficient Storage

Frequently Asked Questions

What does HTTP 507 Insufficient Storage mean?

A WebDAV status meaning the server has run out of storage (disk, quota) required to save the resource. In short: The server cannot store the representation needed to complete the request.

Is a 507 Insufficient Storage error my fault or the website's?

507 is a 5xx server-error code, so the problem is on the server side, not your browser or device. As a visitor you can usually only retry; if you run the site, investigate the server.

How do I fix a 507 Insufficient Storage error?

Free disk space or expand storage. Raise the user/quota limit. Add monitoring and alerts for disk usage.

Official Specification

The 507 Insufficient Storage status code is defined in RFC 4918 Section 11.5.

View the IANA HTTP Status Code Registry →