# Spaces POST: response \[413\] 'request entity too large'

**URL:** <https://discuss.huggingface.co/t/spaces-post-response-413-request-entity-too-large/26723>\
**Category:** Spaces\
**Created:** [November 26, 2022, 12:02am UTC](https://discuss.huggingface.co/t/spaces-post-response-413-request-entity-too-large/26723 "2022-11-26T00:02:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![plexus3d](https://avatars.discourse-cdn.com/v4/letter/p/f08c70/32.png) [@plexus3d](https://discuss.huggingface.co/u/plexus3d)\
**Post date:** [November 27, 2022, 6:16pm UTC](https://discuss.huggingface.co/t/spaces-post-response-413-request-entity-too-large/26723/2 "2022-11-27T18:16:14Z")

</div>

It looks like file size is the issue here when getting these [413] errors from the server: I’ve lowered the payload size progressively to the point where a ~200Kb base64 payload succeeds.

It would be helpful for HF to state an explicit limit, and whether the upload limit changes with a Pro account or when hosting the input URLs in Spaces/Hub v. external domains.

From [this post](https://discuss.huggingface.co/t/using-inference-api-with-large-audio-files/17847/4) it seems that others have problems uploading similarly ‘small’ files.

---

_[View the full topic](https://discuss.huggingface.co/t/spaces-post-response-413-request-entity-too-large/26723)._
