Runs in your browser. Your files and text never leave your device - nothing is uploaded.
5xx Server Error
What it means
The server is unable to store the representation needed to complete the request (WebDAV).
| Property | Detail |
|---|---|
| Status class | 5xx Server Error |
| Defined in | RFC 4918, Section 11.5 |
| Cacheable by default | Only with explicit caching headers: a cache stores it when the response carries Cache-Control (max-age, s-maxage or public) or Expires. |
| Who needs to act | The server owner, or the account holder who is over quota. |
What does HTTP 507 Insufficient Storage mean?
HTTP 507 Insufficient Storage means the server cannot store the representation needed to complete the request, typically because its disk is full or the user's storage quota is used up. It comes from WebDAV, where uploads and copies write data to the server, and the condition is considered temporary until space is freed.
How 507 Insufficient Storage works
RFC 4918 defines 507 for WebDAV methods that write data, such as PUT, COPY, MOVE and MKCOL. It treats the condition as temporary and adds an unusual rule: if the request was the result of a user action, the client must not repeat it until the user asks again with a separate action. Outside classic WebDAV, file-sync services built on it use 507 for quota errors; Nextcloud, for example, returns it when an account has no space left. It is not the same as 413, which rejects one oversized request regardless of how much space is free.
Example 507 request and response
PUT /remote.php/dav/files/ana/video.mp4 HTTP/1.1
Host: cloud.example.com
Content-Length: 2147483648
HTTP/1.1 507 Insufficient Storage
Content-Type: application/xmlA 2 GB upload to a Nextcloud-style WebDAV path when the account's quota has less space than that left.
What causes a 507 Insufficient Storage
- A full disk on the server, or on the volume used for uploads.
- A per-user quota exhausted on a WebDAV or file-sync service such as Nextcloud.
- Copying or moving a large folder into a location without enough space.
- Backups or logs filling the same storage that uploads use.
How to fix a 507 Insufficient Storage
If you are uploading
- Free space in your account, or ask for a larger quota.
- Stop sync tools from retrying the same upload in a loop; RFC 4918 says to wait for a new user action.
If you run the server
- Check disk usage on every volume involved, for example with df -h on Linux, including temporary upload directories.
- Clear old logs, caches and backups, and alert on disk usage well before it reaches 100%.
- Review quota settings for the affected users.
- Say in the error body how much space is left, so client apps can tell users how much to delete.
Related status codes
- 413 Payload Too Large: One request is too large, regardless of free space.
- 503 Service Unavailable: A temporary failure for another reason, such as overload or maintenance.
- 500 Internal Server Error: What software that does not use 507 typically returns when a disk fills up.
Frequently asked questions
The server is unable to store the representation needed to complete the request (WebDAV).
The server has run out of disk space or the account has used up its storage quota.
If you run the server, free up storage space or increase the storage allocation. If it is your account quota, delete files or upgrade.
A server-side one, which is why it is a 5xx code: the server lacks space to store the request. If the limit is your account quota, deleting files or upgrading fixes it; otherwise the server owner has to free disk space.
Sources
Other 5xx Server Error codes
Reviewed by Raja Jahangir · Last reviewed: October 7, 2026