FIND Function in Apple Numbers: Syntax, Examples, and Common Errors

=FIND(search-string, source-string, start-pos)

The returned position refers to the start of the matching text in the original source string, not an offset relative to start-pos. The official page demonstrates =FIND("e","where on earth",8) producing 10, not a search-relative position of 3. Ordinary * and ? patterns do not work as wildcards in this function. Apple’s example also demonstrates a REGEX-based search token, which is distinct from claiming that wildcard syntax works. Source: Apple FIND.

The exact function syntax in this guide comes from Apple’s current Formulas and Functions Help, version 15.4 path, accessed 2026-10-11. That number identifies the help edition; Apple does not establish a first-supported Numbers application version on this function page. Apple describes the Functions Browser in Numbers on Mac, iPhone, iPad and iCloud.com, but the function page does not prove identical behaviour on every older macOS/iOS/iPadOS release. No formula in this guide was run in native Numbers on any platform. Confirm the example in the version your readers use before approval.

Examples below assume a Numbers table with one header row. In a formula inside the same table, A2 means the cell at column A, row 2. In a different table, choose the source cells using the formula editor; a qualified Numbers reference can use Names::A2. Do not mechanically replace it with Excel’s Sheet!A2 syntax. This is covered in Apple’s cell-reference documentation.

Apple’s function syntax guidance shows a comma between arguments in the English reference. If the decimal separator on your device is a comma, manually typed function arguments are separated by semicolons instead. Only the separator changes; argument order does not. For example, type =FIND("-",A2) with a comma in the English style, but =FIND("-";A2) if your formula locale uses a decimal comma. The argument order stays the same.

Create a Numbers table called Catalog, with one header row. Set column A to Text to keep product IDs such as 0097 as four-character codes. Enter these five strings exactly:

Steps: Put the data in A2:A6, enter =FIND("-",A2) in B2, and fill through B6. Every input has exactly two letters before its first hyphen; the first - is therefore in position 3. This is an expected result calculated from the supplied strings, not a screenshot or recorded Numbers execution.

A case-sensitive example

On row 2, =FIND("R",A2) has expected output 9 because the capital R follows the second hyphen. Looking for lowercase r would not find the same character. No error-code spelling is asserted here: the official FIND page documents the case-sensitive search, while actual error presentation must be checked in Numbers during native QA.

In C2, use the optional start position to skip the first hyphen:

=FIND("-",A2,FIND("-",A2)+1)

The inner FIND returns 3; start looking again at character 4, and the next hyphen occurs at character 8. Expected C2: 8. On this specific two-hyphen code format, FIND can be combined with MID to extract the four-character identifier:

=MID(A2,FIND("-",A2)+1,FIND("-",A2,FIND("-",A2)+1)-FIND("-",A2)-1)

Expected output: text 2048. The first hyphen is in position 3, the second in position 8; the ID starts at 4 and spans 8-3-1=4 characters. This is independently checked string arithmetic, not a claim of execution in Numbers. It works only if the source follows the stated delimiter pattern. For a code with missing/extra hyphens, validate structure before extracting.

• No matching text: FIND cannot return a valid start position for an absent case-sensitive substring. Confirm case, punctuation, and the source text; consult the formula editor for the actual error presentation instead of assuming an Excel-specific error label.
• Unexpected position: Positions begin at 1, and spaces count. Inspect text characters instead of counting only words.
• Invalid start position: start-pos must be between 1 and source-string length, inclusive. 0 and values beyond the last character are outside Apple’s documented range.
• Later matches: Setting start-pos changes where to search; it does not reset the position numbering. Nested FIND finds later delimiters.
• Wildcards and case: Apple says ordinary wildcard matching is unsupported in FIND; use SEARCH when matching without case or with wildcards. That page’s full syntax was inaccessible in this batch, so no independent SEARCH parameter claims are made here.
• Wrong reference: A2 uses the table containing the formula. Choose the intended input cell when referencing another table.
• Lost leading zeros: Import product IDs as text; a missing 0 cannot be restored by FIND.

Microsoft Excel documents FIND(find_text,within_text,[start_num]) with case-sensitive matching and one-based positions. However, do not copy specific Excel error codes to Numbers without testing its actual UI. Numbers can use table-qualified forms like Catalog::A2 whereas Excel has different worksheet-reference syntax. Apple’s FIND reference points to SEARCH for case-insensitive work; no unverified SEARCH syntax is given here. Microsoft FIND reference.

• TEXTAFTER — existing owner-source guide for text after a delimiter. Source path checked; live HTTP not accessible.
• TEXTBETWEEN — existing owner-source guide for text between delimiters. Source path checked; live HTTP not accessible.
• REGEX.EXTRACT — existing owner-source guide; the official identifier’s punctuation is preserved. Publication note: Related guide links should be checked in the generated site. Native Numbers execution is not recorded.

• Apple Numbers — function documentation
• cell-reference documentation
• function syntax guidance
• https://support.apple.com/guide/functions/welcome/web

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in Apple Numbers.

• No genuine Apple Numbers screenshots are included; this guide does not use mock application images.