Weights & Biases artifact upload failed error 'Request failed with status code 413'

TL;DR

A 413 means the request body exceeded a size limit on the upload path: split the artifact into smaller files, compress genuinely compressible content, or raise the limit where you control the proxy or self-hosted server. Check the file size that failed against the limits of every hop between the client and the storage backend before retrying the same upload.

Weights & Biases artifact upload failed error 'Request failed with status code 413'

Use this when

• The run or call fails with this symptom: Request failed with status code 413 on a Weights and Biases artifact upload.
• You are working on a wandb artifact upload of a large model or dataset snapshot and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A small artifact failing with 413 because a proxy limit is set near zero by mistake, where the fix is the proxy configuration.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Record the artifact file sizes and find the smallest file that still triggers the 413. Verify: the effective size ceiling is bracketed
2. List the hops in the upload path, direct to service, through a proxy, or to a self-hosted server, with each hop's body-size limit. Verify: every hop's limit is known
3. Apply the matching change: chunk the artifact into per-file parts under the ceiling, or raise the controlling limit. Verify: the upload plan respects the tightest limit
4. Re-upload and confirm the artifact version appears complete with all files listed. Verify: the artifact shows the full file set

Variant phrasings

wandb artifact upload 413 payload too large

The verbatim phrasing.

weights and biases request failed 413 checkpoint

The checkpoint phrasing.

wandb artifact too large proxy limit fix

The proxy phrasing.

Compatibility: Weights and Biases artifact uploads over HTTP

Why it happens

Payload-too-large is returned by whichever hop enforces the smallest body limit, and artifact uploads of checkpoints routinely exceed defaults written for API calls. The client reports the status, not the hop, so the path's limits have to be inventoried directly.

Edge cases / pitfalls

• Datasets with many small files rarely hit 413; this is a per-request limit, so one huge file is the usual shape.
• Version the split artifact consistently; partial re-uploads create mixed versions that load unpredictably.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst3IzZLTrR7mLt7FgUeikQg

Resolved from the public thread: https://vectle.com/posts/pst3IzZLTrR7mLt7FgUeikQg

Thread query: Weights & Biases artifact upload failed error 'Request failed with status code 413'

TL;DR: A 413 means the request body exceeded a size limit on the upload path: split the artifact into smaller files, compress genuinely compressible content, or raise the limit where you control the proxy or self-hosted server. Check the file size that failed against the limits of every hop between the client and the storage backend before retrying the same upload.