Character Length Distribution

Character Length Distribution groups text field values into length-based segments, and compares average length against the field maximum.

Character Length Distribution analyzes text-based fields (for example Description, Subject, custom text fields, and encrypted text) and sorts the character length of every non-blank value into one of five fixed buckets: 0–50, 51–100, 101–255, 256–4,000, and 4,001+ characters. For each field, it also calculates the average character length, the field's configured maximum length, and the percentage difference between the two. This "over-provisioning" percentage shows how much larger the allowed maximum length is compared to actual usage.

Use this analysis to limit field length to the right size, and to check whether a field's real-world usage matches its intended purpose.

Character Length Distribution or Character Length Analysis?

The Character Length Distribution analysis shows the overall shape of a field's length usage: how values are spread across the buckets, and how the average compares to the maximum. To catch individual outlier values (unusually long or unusually short entries within an otherwise normal field), use the Character Length Analysis instead.

Detailed Job Results

The Character Length Distribution donut chart shows each field's values across the five length buckets. Hover over a chart section to see more details.

The Over-provisioned Character Length bar chart ranks fields by their percentage of length difference (average length vs. maximum allowed field length). A 100% or 99% difference points to an empty or almost empty field, while low difference indicates that most of the field length is actually used on many of the records.

The Field Details table lists for each field the maximum allowed character length (Max Length Allowed), the longest value actually present in the data (Max Length Found), the Average Length, and the percentage difference between the average length and the maximum allowed length ( % Difference (Avg vs Max Allowed)).

Key Insights

Over-provisioning: A high percentage difference between average length and maximum length, combined with most values sitting in the lower buckets, means the field's maximum length is configured far larger than what is actually used.
This is primarily a data governance signal rather than a storage-saving opportunity; see the note below.
Truncation risk: When a large share of values fall into the 256–4,000 or 4,001+ buckets, and the average length sits close to the max length, users may be hitting the field's ceiling or already losing data to truncation.
Max Length Found vs. Max Length Allowed: Comparing these two columns directly shows the largest value ever entered, which is useful for judging how much headroom a lower max length would actually leave.
Usage pattern mismatch: The bucket distribution shows whether a field is being used for short labels, medium notes, or long narratives, which may not match what the field was originally designed for.
Reporting and AI readiness: Fields where the max length and average usage are closely aligned give a more stable, interpretable signal for segmentation or AI models than fields that are heavily over- or under-provisioned.

Lowering Max Field Length

Lowering an over-provisioned field's max length does not generally free up data storage. Salesforce charges most objects, including Leads, Contacts, Accounts, and custom objects, a flat amount of storage per record regardless of how much of a text field's length is actually used. The benefit of right-sizing a field is mainly in data governance and platform behavior: keeping a field at 255 characters or under preserves Text field capabilities (such as use as an External ID, a Unique field, or a duplicate rule matching key) that are lost once a field becomes a Long Text Area, and a tighter limit discourages the field from being used as a dumping ground for unrelated content.

Recommended Actions

Scenario	Actions
Over-provisioned field (large max, low average)	- Consider a shorter text type or lower max length for new field designs. - For existing fields, evaluate introducing a shorter replacement field rather than editing the original if backward compatibility is a concern. - Update help text to clarify the intended type and length of content.
Under-provisioned field (average close to max, truncation risk)	- Evaluate whether the field should move to a longer text type, if available. - Split the field into multiple structured fields, such as a summary field plus a details field. - Move longer content to related records, files, or attachments instead of a single text field.
Usage doesn't match intended purpose	- Improve labels, help text, and templates to encourage the expected level of detail. - Provide an alternative container, such as Notes or a related record, for content that keeps overflowing a field meant to stay short.