Salesforce Character Limits: Why the Name Field Request Was Just Closed After a Decade

Salesforce's standard Name field has been capped at 80 characters since the platform's earliest days — long enough for most names, but a real constraint for longer product names, formal business entities, or anything requiring more descriptive identification. In July 2026, after more than a decade of community requests, Salesforce gave its final word on whether that would ever change.

A Decade-Old Request, Closed for Good

The request to extend the Name field from 80 to 255 characters had been one of the most-voted ideas in Salesforce's IdeaExchange community for over ten years. In July 2026, Salesforce officially closed it — not with a quiet dismissal, but with a genuine technical explanation: the Name field is built into foundational infrastructure shared across every custom object, in every organization, across the entire platform. Expanding it would require a massive, platform-wide data migration, and Salesforce concluded the risk to platform stability wasn't worth it.

It's easy to look at a character limit and assume it's just a number in a database waiting to be changed. This particular case is a useful reminder that some limits are load-bearing — the Name field isn't an isolated setting on one object, it's a piece of shared infrastructure that every org on the platform depends on, which is exactly why a decade of requests and thousands of votes still weren't enough to move it.

Field-Level Help Text: The Limit That Did Get Doubled

Not every Salesforce character limit is permanently fixed — field-level help text, the description shown when hovering over a field's info icon, was expanded from 255 to 510 characters back in the Spring '21 release, and that expanded limit is now the permanent standard across Sales and Service. Unlike the Name field, this limit applies automatically with no configuration required, though Salesforce's own documentation is clear that 510 is now hard-coded and won't be increased further either.

Long Text Area: A Different, Still-Open Complaint

Long Text Area custom fields can technically store far more than 255 characters, but content beyond that point becomes invisible specifically within Salesforce's reporting tools — a distinct, still-unresolved pain point with over 2,500 votes on its own IdeaExchange thread. Unlike the Name field's now-closed request, this one remains open, and the practical workaround in the meantime is pulling the full field content through a different export or reporting path rather than relying on the standard report view.

Formula Fields: Two Different Limits at Once

Formula fields carry their own, separate character constraints — a 3,900-character limit on the formula as written, and a considerably larger 15,000-character limit on the compiled version Salesforce actually executes. A formula can exceed the compiled limit even while looking modest in source form, particularly when it references multiple fields or nests several functions, which is why Salesforce's own optimization tooling exists specifically to flag formulas causing this kind of slowdown before they hit the wall.

Checking a Field Against the Right Limit

Since Salesforce's limits vary considerably by field type — some fixed since the platform's founding, some doubled once and then locked, some still under active community debate — checking a specific field's actual constraint before assuming a number applies avoids running into an unexpected wall mid-project. A character counter makes checking any planned field content against its actual limit fast, before that content gets built into a form, integration, or migration that assumes more room than Salesforce will allow.

---

Salesforce's character limits aren't uniform, and they don't all follow the same rules for change — the Name field's 80-character cap just received a final, permanent no after ten years of requests, while other limits like field-level help text have been doubled, and others like Long Text Area's reporting visibility remain genuinely unresolved. Knowing which category a specific limit falls into is what separates a productive workaround from a request that's already been definitively closed.