> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.console/limits.md). # Limits What are the limits to use Blynk platform features {% hint style="success" %} If you are using [Enterprise Plan](https://blynk.io/pricing), the limits below can be increased. Contact your support engineer. {% endhint %} ### HTTPS API Limits Max request size: 2 MB (headers + request body) Max number of file uploads (product/organization logos) per user per day: 0 Free / 50 PRO Max number of **Export Data** calls (`/external/api/data/get`) per device per day (both UI and HTTPS API export): 10 Max number of the **Update** requests (`/external/api/update`) per device per day: 500,000 ### Device Template Limits These are limits that apply to a each device template:
FeatureFREEPRO
Datastreams50200
Events5100
Metadata fields520
Additional device dashboard pages in Blynk.Console-3
Additional pages in Blynk.apps-20 pages total (among them max 7 device Info tabs, 1 welcome page)
Tabs in Tabs widget in Blynk.apps-20
``` Limitations ``` ### Assets | Feature | Details | | -------------------------- | ------------------------------- | | **Supported formats** | `.png`, `.jpg`, `.jpeg`, `.ico` | | **Max files per upload** | 50 files | | **Max file size** | 5 MB per file | | **Storage per template** | 200 MB | | **Max files per template** | 1,000 files | | **Max file name length** | 1,000 characters | ### Organization Limits These are limits that apply to any organization (that includes all it's sub-organizations):
FeatureFREEPRO
Templates1050
Devices550
Device messages100,000/monthUnlimited
Automations per sub-organization550
Actions per automation550
Automation push/emails per hour2020
Users150
Sub-organizations-200
Levels of sub-organizations hierarchy-4
Blynk.Air shipments (campaigns)225
Locations250
Webhooks1100
Total file uploads (logos, etc.)050
Max logo image size: 4096x2048 pixels Report file expiration time: 45 days Max user invites per day: 25 invites ### Tags Limits Max number of tags per organization: 20 Max number of tags per device: 5 Max number of tags per user: 5 ### Webhooks Limits Max response size: 16 KB Max URL length: 1024 chars Max body size: 5 KB Max number of Webhooks per organization: 1 for Free, 100 for PRO plan. requestsLimit rate: 10 request per minute per webhook ### Hardware Max number of events per day per device (`Blynk.logEvent`): 100 events Min interval between events of the same type: 1 second Min interval between notification messages (push notifications/emails/SMS): 5 seconds Max number of requests per device: 50 requests/second Max number of data points per device per day you can import into the device: 10,000 points Max length of the string value: 1024 bytes ## UI The maximum number of real-time updates on the web/app can accept - 20 commands per second --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.blynk.io/en/blynk.console/limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.