ArcGIS Arcade String Functions: Names and Examples

Formulas & functions · Updated November 22, 2026

ArcGIS Arcade string functions are built-in tools for finding, joining, extracting, replacing, and changing text in an expression. The core functions include Concatenate, Find, Left, Mid, Right, Split, Replace, Lower, Upper, Proper, Trim, StartsWith, and EndsWith; which ones you can use depends on the Arcade version supported by the ArcGIS app or service running the expression.

What Arcade string functions do

Arcade is Esri’s expression language for working with GIS data and presentation. String functions operate on text values such as feature attributes, labels, pop-up content, and values assembled from several fields. For example, an expression can combine a street name and type, standardize inconsistent capitalization, or extract a code from a longer identifier.

Arcade is not a general-purpose substitute for Python or SQL. An expression runs in a particular Arcade profile, such as a labeling, visualization, or pop-up profile, and that profile provides its own inputs and expected output. In a feature-based expression, $feature refers to the current feature, so $feature.RoadName reads its RoadName attribute. The same string operation can be useful in more than one profile, but the surrounding expression and available data may differ.

The main functions and their jobs

These functions cover the common text operations. Check the Arcade documentation for the version used by your target product if an expression must work across different ArcGIS releases.

  • Concatenate(values, separator) joins values, optionally placing a separator between them.
  • Find(searchText, text, startPos) returns the position of a matching substring, or -1 if it is not found.
  • Left(value, numChars) and Right(value, numChars) return a set number of characters from the beginning or end.
  • Mid(value, startPos, numChars) returns a section of text starting at a specified position.
  • Split(value, separator) divides text at a delimiter and returns an array of pieces.
  • Replace(value, searchText, replacementText) replaces matching text with another string.
  • Lower(value), Upper(value), and Proper(value) change letter casing.
  • Trim(value) removes leading and trailing whitespace; StartsWith(value, searchText) and EndsWith(value, searchText) test the ends of a string.

Function names and argument order matter. For example, Find takes the text to search for first and the larger text second. That order is easy to reverse if you expect it to behave like a sentence in English.

Joining fields and cleaning values

Concatenate is handy for labels and display strings. Suppose a feature has FirstName and LastName attributes. This expression joins their values with a space:

Concatenate([$feature.FirstName, $feature.LastName], " ")

The array supplies the values, and the second argument supplies the separator. A comma, slash, or other delimiter can be used instead. Think about missing attributes before building a production expression: a null or blank field can lead to an incomplete-looking result. Use IsEmpty to check for empty or null values when the desired behavior needs to be explicit, and build the output conditionally rather than assuming every record is complete.

Case functions can help normalize data for display or comparisons. For example, Upper($feature.StateCode) can show a state code in uppercase, while Lower($feature.Email) can make an email address display consistently. Proper applies title-style capitalization, which can be convenient for names or place labels, but it is not a reliable correction for every proper noun: it may alter acronyms, brand names, and intentional capitalization. Keep the original value if those distinctions matter.

Trim is useful when imported data contains accidental spaces at the start or end of a value. It does not correct internal spacing or inconsistent punctuation. For example, trimming a street name will not turn multiple spaces between two words into one; that requires additional logic or a different data-cleaning step.

Finding and extracting part of a string

Find is useful when the location of a delimiter or word matters. It returns a zero-based position: the first character is at position 0. A result of -1 means the searched-for text was not present. For example:

Find("@", $feature.Email)

This returns the position of the at sign in an email field, or -1 if there is none. A position check can help distinguish a plausible input from one that lacks a required character, although it does not validate that an email address is genuinely usable.

Use Left, Mid, or Right when the text has a known structure. If a code such as NW-4827-X always has the same layout, a fixed-position extraction can return its first two characters or a segment from its middle. Mid uses a starting position and a character count; its starting position follows the same zero-based convention. Fixed positions are fragile if the source format changes, so prefer a delimiter-based approach when lengths vary.

StartsWith and EndsWith answer a different question: whether a value begins or ends with a given string. They return a Boolean result, which can be used in a conditional expression. For example, testing whether a parcel identifier ends in a known suffix can help classify records without extracting the suffix first.

Splitting text at a delimiter

Split turns one string into an array of strings. For a Categories attribute containing parks;trails;water, this expression separates the values at semicolons:

Split($feature.Categories, ";")

The result is an array, not one text string. That distinction matters: you can use array operations to inspect or work with the pieces, but you should not treat the result as though it were a regular string. If a field contains a comma-separated list, splitting at commas is appropriate only when commas are truly separators. A value such as a quoted address or a name that itself contains a comma can require more careful parsing.

Splitting is also useful for extracting a section from a consistent, delimiter-separated identifier. Before relying on a particular array position, consider what happens if a record has a missing delimiter, an extra delimiter, or a blank value. Validate the number of pieces or handle empty input so a formatting irregularity does not create an unexpected result.

Choosing the right function for a task

Start with the shape of the problem rather than the function name. If you need to join multiple attributes, choose Concatenate. If you need to know where a substring occurs, use Find. For a fixed-length prefix or suffix, use Left or Right; for a known section in the middle, use Mid. Choose Split when a delimiter separates multiple pieces, and Replace when one literal fragment should be changed.

  • For consistent display capitalization, use a case function, but confirm that changing case will not damage meaningful acronyms.
  • For extra spaces at the edges, use Trim; for a condition based on a prefix or suffix, use StartsWith or EndsWith.
  • For numeric or date attributes displayed as text, consider the general Text function and its formatting options instead of assuming a string function will format the value correctly.
  • For inconsistent source data, decide whether the expression should fix presentation only or whether the underlying dataset should be cleaned. A display expression does not rewrite the stored attribute.

One common misconception is that string expressions automatically update the source field. In most Arcade uses, the expression calculates a result for a particular purpose, such as a label, pop-up, or renderer. Editing the actual data is a separate workflow. Use an appropriate editing or data-management tool if the goal is to permanently standardize stored values.

Version, profile, and data considerations

Arcade capabilities have evolved, and ArcGIS products do not all run the same Arcade version. An expression that works in one recent application may use a function unavailable in an older deployment. The profile also defines which variables and data are available. For example, a feature expression commonly uses $feature, but an expression intended for another profile may have different inputs or output requirements.

When sharing an expression, check the target application’s Arcade version and the profile documentation, not just whether the expression editor accepts the syntax in your current environment. This matters for web maps consumed by older clients, hosted workflows, and expressions moved between ArcGIS products. Keep expressions straightforward when broad compatibility is important, and test them against representative records, including nulls, blank strings, punctuation, and unexpected formats.

Common problems and how to avoid them

  • Reversed arguments: For Find, put the substring first and the value to search second.
  • Off-by-one extraction: Positions for Find and Mid start at zero. Check the first and last characters with a short example before applying fixed positions to an entire layer.
  • Unexpected no-match result: Find returns -1 when there is no match. Do not use that result as if it were a valid character position.
  • Confusing arrays with strings: Split returns an array. Use an array-aware operation when you need an element or need to process the pieces.
  • Over-cleaning text: Changing case or replacing a fragment can make names less accurate. Preserve original attributes when the display version is not authoritative.
  • Null and empty values: Use explicit checks when a field may be absent. An expression should define what to show for incomplete records rather than relying on a guess about the input.

Debugging is easier if you test one operation at a time. First inspect the source attribute, then test the extraction or match, and finally add formatting or conditional logic. A short test set should include an ordinary value, a value with no delimiter, a blank value, and one with an unexpected character. This reveals assumptions that a single ideal record would hide.

Frequently Asked Questions

What is the Arcade function for combining strings?
Concatenate joins an array of values, with an optional separator between them. For instance, it can combine a feature’s first and last name with a space.

Is there a substring function in Arcade?
Use Mid(value, startPos, numChars) to return a portion from a chosen position. Use Left or Right for a specified number of characters at either end.

How do I find text in an Arcade string?
Use Find(searchText, text). It returns a zero-based position when it finds a match and -1 when it does not.

Does Arcade have a function to split text?
Yes. Split(value, separator) divides a string at the separator and returns an array. Remember that the output is an array rather than another string.

Can Arcade change the stored attribute value?
A string expression normally calculates a result for its profile, such as a label or pop-up; it does not by itself edit the source attribute. Use an editing or data-management workflow to permanently change stored data.

Related

Try it: the Formula Explainer: paste any formula and see each function and reference in plain English.

More in Formulas & functions

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.