TEXTAFTER Function in Zoho Sheet: Syntax, Examples and Troubleshooting
Extract text after a delimiter in Zoho Sheet, using occurrence numbers, case matching, a missing-match fallback and reproducible examples.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =TEXTAFTER("North-Widget-0042";"-") returns Widget-0042. By default, the function uses the first occurrence of the delimiter and a case-sensitive search. The delimiter itself is excluded from the result.
Availability and version history
- Introduced: Added in March 2023, according to Zoho’s release history; no numbered cloud release is given.
- Availability: Currently documented in Zoho Sheet’s rolling web-service help; no retirement or final supported release is identified in the checked sources.
- Scope: The web documentation establishes these options; mobile and imported-workbook behavior are not separately certified here.
- Checked: October 14, 2026, using the official TEXTAFTER reference, with independent string-result checks. No native Zoho Sheet test.
Syntax and defaults
=TEXTAFTER(text; delimiter; [instance]; [mode]; [match_end]; [if_not_found])
| Argument | Role | Required or default |
|---|---|---|
text |
Original text or a cell containing it | Required |
delimiter |
Literal text marking the boundary | Required |
instance |
Which occurrence to use; a negative integer counts from the end | Default 1 |
mode |
0 for case-sensitive matching; 1 to ignore letter case | Default 0 |
match_end |
1 treats the end of the text as a delimiter; 0 does not | Default 0 |
if_not_found |
Text returned when no valid match exists | Default is a not-found error |
The bracket notation marks optional arguments; do not type the brackets. These examples follow Zoho’s semicolon-separated syntax. A quoted delimiter such as "::" is a text boundary, not a character-count argument. The official reference documents the defaults and search direction.
Reproducible worksheet
Create headers in A1:G1: Input, Delimiter, Instance, Mode, Fallback, Result, Check. Enter the following text and numeric values in A2:E9. Type cell text without enclosing quote characters; quotation marks are needed for text literals written directly inside formulas.
| Row | A: Input text | B: Delimiter | C: Instance | D: Mode | E: Fallback | Expected F |
|---|---|---|---|---|---|---|
| 2 | North-Widget-0042 |
- |
1 | 0 | Review |
Widget-0042 |
| 3 | North-Widget-0042 |
- |
2 | 0 | Review |
0042 |
| 4 | North-Widget-0042 |
- |
-1 | 0 | Review |
0042 |
| 5 | Red|Blue|Green |
| |
-2 | 0 | Review |
Blue|Green |
| 6 | RedENDGreen |
end |
1 | 0 | No match |
No match |
| 7 | RedENDGreen |
end |
1 | 1 | No match |
Green |
| 8 | plain |
| |
1 | 0 | Review |
Review |
| 9 | tag::value |
:: |
1 | 0 | Review |
value |
In F2, enter =TEXTAFTER(A2;B2;C2;D2;0;E2) and fill down to F9. Explicit match_end=0 ensures that a genuinely missing delimiter uses the fallback. The first two rows differ only in occurrence number; rows 6 and 7 differ only in case-matching mode.
In G2, enter =TEXTAFTER(A2;B2). Its expected result is Widget-0042, matching F2 because the optional defaults are the same in this case. The full-column formula keeps the fallback explicit so unstructured rows remain visible for review rather than disappearing into blank-looking results.
Search direction and fallback choices
An instance of -1 selects the last delimiter; -2 selects the second-last. The returned string retains its original reading order. It is not reversed. This is useful when the last separator identifies a suffix but earlier separators are legitimate parts of the name.
For a missing delimiter, =TEXTAFTER("plain";"|";1;0;0;"Review") returns the fallback Review under the documented no-match rule. A fallback does not repair the record. Keep it distinctive enough to find and investigate, especially before grouping or joining data.
match_end=1 changes the boundary rule and can therefore prevent a missing literal separator from producing your fallback. The worked data leave it at zero. The short help does not fully specify its interaction with negative occurrence numbers, empty delimiters or overlapping matches; those combinations are outside these examples.
Advanced example: extract and clean a labeled value
Keep the first table unchanged. In A12, type Team: East with two spaces after the colon. In B12, enter =TEXTAFTER(A12;":"). The expected text begins with two spaces, followed by East. In C12, enter =TRIM(B12); the expected result is East. TRIM removes the surrounding spaces, but you should only normalize whitespace when that suits your data.
To extract a middle field from the original structured identifier, put this formula in F12:
=TEXTBEFORE(TEXTAFTER(A2;"-");"-")
The inner result is Widget-0042; the outer result is Widget. TEXTBEFORE’s official reference documents the second boundary operation. This two-stage approach assumes exactly the separator structure shown; a product name containing additional hyphens needs a different schema.
The suffix 0042 in F3/F4 is text. Preserve it as an identifier if its leading zeros matter instead of immediately converting it into the number 42. LEN can help check text lengths when validating such extracted codes.
Errors and troubleshooting
- No valid match: check spelling, delimiter and mode before replacing the error with a fallback. Zoho’s page writes
#N/Ain the argument description and#N/A!in its error table; the precise displayed spelling has not been observed here. - Wrong occurrence: count delimiter occurrences, not letters in the string. Start with a positive integer such as 1 or 2, or -1 for the final occurrence.
- Text treated as a name: put literal text inside double quotes when writing it directly in a formula; cell references such as A2 are not quoted.
- Invalid reference or input type: Zoho lists
#REF!for broken references and#VALUE!for unsuitable types. A broad IFERROR wrapper can hide these different causes; the function’s own fallback is more targeted to a missing match.
The TEXTAFTER page does not list every occurrence-number error individually. Exact behavior for zero or fractional instances is not inferred from another application or from TEXTBEFORE’s separate error table.