The short version: Microsoft doesn't publish a fixed maximum for controls per screen or per app, as at 22 September 2026, only a warning that apps with thousands of controls and hundreds of data sources slow down. What it does publish exact numbers for: 64 MB per media file, 200 MB of media total, and the 500-to-2,000 record window covered in the delegation limit post.
What is documented, and what isn't
| Limit | Documented value | Source |
|---|---|---|
| Media file, individual | 64 MB maximum | Power Apps canvas app media limits |
| Media files, total per app | 200 MB maximum | Power Apps canvas app media limits |
| Data row limit, default / maximum | 500 / 2,000 | Canvas app delegation guidance |
| Controls per screen or app | Not a published number | Guidance only: "thousands of controls... slows Studio" |
| Data sources per app | Not a published number | Guidance only: "hundreds of data sources... slows Studio" |
Search for "maximum controls per canvas app screen" and you won't find a number on Microsoft Learn, because there isn't one to find. Microsoft's own performance guidance describes apps that grow to thousands of controls and hundreds of data sources, as a description of what starts to slow Power Apps Studio down, not a ceiling with a figure attached. What is a hard, enforced number is media: a single image, audio or video file can't exceed 64 MB, and every media file added to the app, added together, can't exceed 200 MB. Both are hit at upload time, not discovered later as a performance complaint.
Where the real ceiling actually sits
For a firm under 20 staff, the practical limit is rarely a hard number anyway, it's the point where Power Apps Studio itself gets slow to work in, and where the app takes longer to load for the person using it. Microsoft's own advice for a large or complex app is to partition it: split it into separate canvas apps that hand off to each other with the Launch function, or move a section into a model-driven custom page, rather than one screen carrying every control the app will ever need. A canvas app compared against a model-driven or code-first build is the decision to revisit once an app is genuinely outgrowing this shape, not a documented control count.
The number that does bite predictably, and far earlier than any controls count, is the 500-record default on a non-delegable query, raisable to 2,000. That's covered in full, including which functions actually delegate, in the Power Apps delegation limit post; it's worth reading before assuming a sluggish app is a controls problem rather than a data problem.
Common questions
Is there a maximum number of controls allowed in a Power Apps canvas app?
No fixed number. Microsoft's own guidance says apps that grow to thousands of controls and hundreds of data sources slow down Power Apps Studio, and recommends partitioning large apps into separate canvas apps or model-driven custom pages, rather than publishing a specific maximum.
What is the media file size limit in a canvas app?
64 MB for a single media file, and 200 MB for the total of every image, audio and video file uploaded to the app. Both are hard limits enforced when you add the file, not a performance recommendation.
How many records does a canvas app pull from a data source by default?
500 by default for a non-delegable query, raisable to a maximum of 2,000 in the app's Data row limit setting. That's a separate limit from controls or app size, and it's covered in full in the delegation limit post.
App getting slow to open or edit?
Free 30-minute call. Tell me roughly how big it's got and I'll tell you whether it's a data problem, a controls problem, or time to split it.