Document Strapi Cloud upload size limits

[giu1io]

This PR adds an "Upload size limits" section to the Cloud Upload page, covering the 200MB infrastructure cap for non-image files and per-plan memory-based recommendations for image uploads by format. Cross-links are added from the Cloud Middlewares page and the CMS Media Library "Max file size" section.

Direct preview link 👉 here

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview, Comment	Jun 12, 2026 2:01pm

[markkaylor]

Nice, looks good to me!

[markkaylor]

You should probably wait for @pwizla approval though

[mariekirsch]

Made some structure changes to the Upload Provider Configuration for Strapi Cloud page so it flows better and explicitly covers more than the configuration of third-party upload provider

[giu1io]

Made some structure changes to the Upload Provider Configuration for Strapi Cloud page so it flows better and explicitly covers more than the configuration of third-party upload provider

Looks good to me, do we want to get @pwizla input too?

[pwizla]

Thanks for putting this together. The upload size limits have been a recurring source of confusion, so documenting them is genuinely valuable. The cross-linking between media-library.md, middlewares.md and upload.md is well done, every anchor resolves, and the technical claim about the infra-level cap being un-overridable via strapi::body checks out against the body middleware implementation.

I do have one structural concern that I'd like us to resolve before merging, plus a handful of smaller polish items.

Main point: the size-limits content doesn't belong at the top of this page

This page is titled "Upload Provider Configuration for Strapi Cloud", but the PR inserts the new "Strapi Cloud upload size limits" section (~55 lines) above the actual provider-configuration content. A few things make me think this isn't the right home for it:

• Title vs. content mismatch. A reader landing here (from the sidebar, search, or the new cross-links) expects to start configuring a provider, but now scrolls past plan caps and megapixel tables first. The page now covers two distinct topics but the H1 only names one. The Tldr and description were updated to mention size limits, but the H1 wasn't, so the page is internally inconsistent.
• The two topics are orthogonal, and the PR says so itself. The new section explicitly notes that switching to S3/Cloudinary "is not a workaround" for the memory limits. So size limits aren't a prerequisite for configuring a provider; placing them first forces every provider-config reader through unrelated content.
• This content wants to be a reference page. Both middlewares.md and media-library.md now deep-link to #strapi-cloud-upload-size-limits as the single source of truth. Three pages depend on it as a destination, yet it lives as a preamble under a mismatched title.

Suggestion (in order of preference):

1. Extract "Strapi Cloud upload size limits" into its own dedicated page (e.g. docs/cloud/advanced/upload-size-limits.md, sitting next to this one), and point all three cross-links at it. I checked whether an existing Cloud page could host it. usage-billing.md was the closest, but it's framed around storage quotas and billing overages ("how much will I be charged after exceeding limits"), whereas this content answers "what can I upload" before uploading, so it doesn't belong there. None of the other Cloud pages (caching, cloud-fundamentals, settings, and so on) fit either. A dedicated page is the cleanest option and breaks no links: just update the anchors.
2. Failing that, move the section below the provider-configuration steps on this page.
3. At minimum, if it stays at the top: broaden the H1 (e.g. "Upload Configuration for Strapi Cloud") and the Tldr so the title honestly reflects both topics.

Side effect of the restructuring: the "4 steps" framing is now off

Demoting ## Deployment to ### Deployment is mechanically fine (no broken hierarchy), but the intro still says the setup "requires 4 steps" and lists 4 ### headings, so the nested ### Deployment now reads as a phantom 5th step. As a separate ## it was a clearly distinct phase. Either update the "4 steps" sentence to acknowledge deployment as a closing step, or rename it to read as an explicit step (e.g. "Deploy the changes").

Worth fixing before merge

• Overuse of bold (style guide Rule 12). The new section leans heavily on bold for emphasis: setting names, plan tiers, "recommendation", "in-process", "Processing on/off" and more are all bolded, with several paragraphs carrying more than 3 bolded terms (the style-checker flags >3 per paragraph). Per Rule 12 ("Don't overuse capital letters and bold: use proper content formatting instead"), emphasis should come from structure, not bold runs. Reserve bold for genuine UI labels, and let admonitions, tables, and headings carry the rest.
• The megapixel tables are hard to act on. They're expressed in MP per format per plan, across two tabs, but readers know their file size in MB or their pixel dimensions, not megapixels. Answering "can I upload this image?" takes several mental steps, and the actionable advice ("disable both settings to upload larger images") sits after the tables. Consider surfacing the actionable guidance up front and/or adding a pixel-dimension column alongside MP.

Minor polish (mechanical, non-blocking)

• upload.md: headings use Title Case; Strapi convention is sentence case: Install the Provider Plugin becomes "Install the provider plugin", same for Configure the Provider, Configure the Security Middleware, Strapi Cloud Configuration.
• upload.md: 3rd-party (L107) should be third-party (matches the rest of the page); ./config/... paths should be /config/....
• media-library.md: em dash at L406 should be a colon or comma per the style guide.
• Consistency: "200MB" vs "200 MB" varies even within upload.md (L20 vs L31); normalize on "200 MB".
• Pre-existing, but worth fixing while we're here: media-library.md L112 states the sizeLimit default as 209715200 (200 MB), but the real default in packages/core/upload/server/src/config.ts is 1000000000 (1 GB), same for the "default of 200MB" prose at L255. This now sits right next to the new Cloud note, so the contradiction is more visible.

Happy to pair on the restructure if useful. The content itself is solid, it's really just a question of where it lives. 🙏