Slack error view_too_large: View payload exceeds 250kb
Last verified against Slack API reference - chat.postMessage errors
Error returned if the provided view is greater than 250kb.What error view_too_large means
The view object you sent is bigger than Slack accepts. The views.open reference says this is "returned if the provided view is greater than 250kb," and the same error is listed for views.update, views.push and views.publish. The limit is on the view payload as a whole, not on any single block.
Hand-written modals rarely get near it. The views that do are data-driven: a Home tab that renders every open ticket, a select menu with thousands of static options, long text pasted into sections, or private_metadata used to carry a large state object between steps. Because the size depends on data, the same code can work for months and then fail for the customer with the most records.
Retrying will not help. You have to send less: paginate, summarize, or move large lists to external data sources that load options on demand.
What it looks like
POST /api/views.publish
{"user_id": "U0123ABCDEF", "view": {"type": "home", "blocks": [...]}}
{"ok": false, "error": "view_too_large"}Why it happens
- A Home tab or modal renders an unbounded list of records.
- Static select menus include very large option lists.
- private_metadata carries a large serialized state object.
- Long text or many repeated blocks were generated from user data.
How to fix Slack error view_too_large
- 1Measure the JSON size of the view before sending and log it alongside the error.
- 2Paginate long lists with Next/Previous buttons that call views.update.
- 3Replace large static selects with external_select so options load on demand.
- 4Store state server-side and keep only an ID in private_metadata.
- 5Summarize or truncate long text with a link to the full content.
How to stop it recurring
Put a size budget into the view builder: cap list lengths, paginate by default, and fail a test when the largest fixture view gets close to 250kb. Test with data volumes from your biggest customer, not with demo data. Log the view size alongside each publish to see growth over time.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- invalid_blocks: Blocks are not validBlocks submitted with this message are not valid.
- msg_too_long: Message text is too longMessage text is too long.
- hash_conflict: View hash does not match current stateError returned when the provided hash doesn't match the current stored value.
- invalid_trigger_id: trigger_id is malformedThe trigger_id is invalid. The expected format for the trigger_id argument is…
Error view_too_large - quick answers
What does Slack error view_too_large mean?
The view object you sent is bigger than Slack accepts. The views.open reference says this is "returned if the provided view is greater than 250kb," and the same error is listed for views.update , views.push and views.publish . The limit is on the view payload as a whole, not on any single block. Hand-written modals rarely get near it.
How do I fix Slack error view_too_large?
1. Measure the JSON size of the view before sending and log it alongside the error. 2. Paginate long lists with Next/Previous buttons that call views.update. 3. Replace large static selects with external_select so options load on demand. 4. Store state server-side and keep only an ID in private_metadata. 5. Summarize or truncate long text with a link to the full content.
Should I retry after error view_too_large?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Slack by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.