# REQUEST_TOO_LARGE

**What it means.** The request carried more than 1 MB, which is more than an app can be sent in one request.

**What to do.** Upload files straight to the app's storage instead of posting them to the app: ask the platform for an upload link (POST /_platform/upload-url) and send the file there. That route answers somebody the app knows — a signed-in visitor, the owner, or an api-kind app's key — so in a public app the upload has to be made by the app's own server code, using UARPIE_STORAGE_BUCKET and UARPIE_STORAGE_PREFIX. Forms and other posts must stay under 1 MB.

- HTTP status: 413
- Retryable after applying the fix: no

Every failure from the CLI or an MCP tool has this shape:

```json
{
  "ok": false,
  "code": "REQUEST_TOO_LARGE",
  "message": "The request carried more than 1 MB, which is more than an app can be sent in one request.",
  "fix": "Upload files straight to the app's storage instead of posting them to the app: ask the platform for an upload link (POST /_platform/upload-url) and send the file there. That route answers somebody the app knows — a signed-in visitor, the owner, or an api-kind app's key — so in a public app the upload has to be made by the app's own server code, using UARPIE_STORAGE_BUCKET and UARPIE_STORAGE_PREFIX. Forms and other posts must stay under 1 MB.",
  "file": "<where to edit, when known>",
  "retryable": false,
  "docs": "https://docs.uarpie.app/errors/REQUEST_TOO_LARGE"
}
```

Apply `fix` (edit `file` when it is given), then run the same command again.