---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/90018#article
headline: "90018: 'Template' field is too long"
url: https://www.twilio.com/docs/api/errors/90018
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 90018: 'Template' field is too long

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when your Broadcast request includes a `Template` value that exceeds the allowed length for that field. Broadcasts are one-time SMS or email campaigns in Twilio Engage, and Engage campaigns can use Twilio services to power SMS delivery.

### Possible causes

* Your request includes an inline `Template` value that is longer than Twilio accepts.
* You added too much static copy, personalization text, or other message content to the `Template` field, which caused the request to exceed the field limit.
* You meant to send a saved template by reference, but sent a long inline `Template` body instead. Use `TemplateSid` with `TemplateLanguage` to reference a saved template.

### Possible solutions

* Shorten the text in `Template` and resend the request.
* Remove unnecessary copy from the inline template so only the content required for the campaign remains in `Template`.
* If you want to reuse message content across campaigns, use a saved template reference instead of sending a long inline `Template` value. Provide `TemplateSid` and `TemplateLanguage` when you use a saved template, and do not send `Template` in the same request.
* Review the content you send through Engage before you launch the Broadcast. If you manage reusable messaging templates, keep them concise and update the template content before resending.

#### Additional resources

* [Audiences, Journeys, and Broadcasts](/docs/segment/guides/audiences-and-journeys)
* [Engage Settings](/docs/segment/engage/settings)
* [Twilio Content Template Builder](/docs/content)