HubSpot Character Limits: The 65,536-Character Field Nobody Notices

A HubSpot CRM note allows up to 65,536 characters — confirmed directly by HubSpot's own developer documentation. That's roughly 10,000 to 13,000 words, far beyond what most people picture when they think of a "note" field, and large enough that hitting the ceiling in practice is genuinely rare.

Where the Limit Actually Comes From

65,536 isn't an arbitrary marketing number — it's 2^16, a classic technical ceiling that shows up in database field types built around 16-bit length prefixes (a TEXT column in many database systems caps out at exactly this figure). Recognizing that pattern is useful beyond HubSpot specifically: a limit that lands on 65,536, 4,294,967,295, or similarly binary-shaped numbers usually signals an underlying database constraint rather than a deliberate product decision about how much text is "enough."

The Same Field, Two Different Rules

HubSpot's own knowledge base confirms a genuine inconsistency: when a multi-line text property value is entered directly through the CRM, it's capped at 65,536 characters — but when the same property is submitted through a form instead, there's no limit at all. A transcript or long document that fits comfortably through a form submission could exceed the CRM's own paste limit if entered the other way, which is a distinction worth knowing before assuming the two entry points behave identically.

A field with two different limits depending on how the text arrives isn't a bug exactly — it's what happens when a system was built by different teams solving different problems at different times, and nobody went back to unify the rules once both paths existed. The practical result is the same either way: knowing which entry point is being used matters more than knowing the field's name.

Subject Lines: A Big Number, a Much Smaller Practical One

Email template subject lines technically allow up to 256 characters, but HubSpot's own guidance recommends staying under 45 to ensure the full line displays without truncation across different email clients and devices. The gap between the technical ceiling and the practical recommendation here is large — nearly 6x — making this a case where "what the system will accept" and "what will actually work" are very different numbers.

Snippets and the Double-Byte Trap

Snippets are capped at 2,500 characters, with an explicit caveat in HubSpot's own documentation: content in a double-byte language like Japanese can hit that ceiling well before reaching 2,500 visible characters, since each double-byte character consumes more of the underlying limit than a single-byte Latin character does. This mirrors a pattern seen elsewhere in this series — Google Ads' double-width character counting, SMS's Unicode encoding switch — where the platform's character count and its actual byte-level accounting aren't the same thing.

Dropdown Options Have Their Own Combined Limit

Each option in a dropdown, checkbox, or radio-select property is capped at 3,000 characters total — covering the label, the stored value, and the description together, not 3,000 characters for each individually. A property with a detailed description and a long internal value could hit that combined ceiling well before the visible label text looks anywhere close to long.

Checking Text Against the Right Field

Given how differently these limits behave — a subject line where the practical number matters more than the technical one, a note field where the entry method changes the actual ceiling, a snippet where language affects the real limit — checking a draft's exact character count against the specific field and entry method it's headed for avoids assuming one HubSpot limit applies uniformly across the platform. A character counter makes checking any individual field fast before assuming it will fit.

---

HubSpot's character limits range from a generous 65,536-character note field most users never approach, to a subject line where the technical ceiling and the practical recommendation differ by a factor of nearly six. The inconsistency between CRM entry and form entry for the same field type is the detail most likely to cause a genuine surprise — worth knowing before assuming a limit that worked one way will behave identically the other.