---
schema_version: "1"
id: 833c5041ab8a3a79232bbf42a81f2336ad505988239ca8440cdff259e7d21cb9
title: SMS Limits and Guidelines
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_overview_limits_sms.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_overview_limits_sms.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a5f1c7a5a080974ce1939b31f83f1a1d415588f4e242c1681900f7f7256af4fe
description: Get to know the limits that apply to sending SMS messages in MobileStudio.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# SMS Limits and Guidelines

Get to know the limits that apply to sending SMS messages in MobileStudio.

## SMS Message Length Limits

The maximum number of characters in an SMS message depends on how the characters are encoded. All unaccented Latin characters are part of the encoding system known as the GSM 03.38 character set. A single message can contain up to 160 characters, as long as it only contains characters in the GSM 03.38 character set. If a message contains one or more characters that aren’t in the GSM 03.38 character set, it’s encoded using a different encoding system called UCS-2. A message that’s encoded using UCS-2 can contain up to 70 characters.

If a message contains more than 160 GSM 03.38 or 70 UCS-2 characters, the message is split into separate message parts. These message parts can be joined on the recipient’s device so that they appear as a single message. The process of joining messages is called concatenation. Support for concatenation varies depending on the recipient’s country, carrier, and mobile device.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52812e46">Resource</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52812e49">Maximum</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52812e52">Details</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Resource" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e46 ">Maximum number of characters in a single message</td>

            <td data-label="Maximum" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e49 ">
              <ul>
                <li>160 GSM 03.38-encoded characters</li>

                <li>70 UCS-2-encoded characters</li>

              </ul>
            </td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e52 ">―</td>

          </tr>
          <tr class="">
            <td data-label="Resource" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e46 ">Maximum number of characters per message part for a multi-part message</td>

            <td data-label="Maximum" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e49 ">
              <ul>
                <li>153 GSM 03.38-encoded characters</li>

                <li>67 UCS-2-encoded characters</li>

              </ul>
            </td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e52 ">Each multi-part message contains hidden information that identifies the message that
              comes before it in order. This extra information reduces the number of characters that are
              allowed in a single message part.</td>

          </tr>
          <tr class="">
            <td data-label="Resource" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e46 ">Maximum number of message parts in a multi-part message</td>

            <td data-label="Maximum" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e49 ">10 message parts</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d52812e52 ">Different carriers around the world have different limits. Salesforce doesn’t strictly
              enforce this limit. We provide this number as a guideline for obtaining the best results
              across different countries, carriers, and devices.</td>

          </tr>
        </tbody>
      </table>

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_tip.png)

Tip

If you copy and paste text from a word processor into your SMS messages, make sure that it hasn’t replaced characters with similar-looking characters. For example, word processors often replace straight quotes (") with curly quotes (“ and ”). Although these characters look similar, they’re not the same. Straight quotes are part of the GSM 03.38 character set, but curly quotes aren’t.

If you include curly quotes in a message that otherwise only contains GSM 03.38 characters, the entire message is sent using UCS-2 encoding. This change in encoding reduces the maximum length of the message by more than half.