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

=PROPER(source-string)

There are no optional locale, case-sensitivity, language, or word-break arguments on the official PROPER function page. For example, Apple explicitly shows =PROPER(60) returning text "60", not a numeric transformation. Never mistake text conversion for numeric formatting. Official Apple PROPER.

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. This one-argument function needs no argument separator by itself, but combined formulas using IF or other multi-argument functions must follow the formula locale.

Create a Numbers table named Names. Make column A a text column, and type the following rows exactly, preserving the capitalization and internal spaces. Put the formula in column B of the same table, not in its input column A.

Steps: Enter the headers, type A2:A6, select B2 and enter =PROPER(A2), press Return, then fill the formula through B6. A2 is text, not a header. For B2, jANE becomes Jane, and DOE becomes Doe; other letters become lowercase. Expected output is Jane Doe. All five results are calculated expectations, not app-captured results.

Paste the literal text mARy-jANE into A7, including two ordinary spaces at each end. In B7, enter:

=PROPER(TRIM(A7))

Expected B7: Mary-Jane. This combines basic space cleanup with Apple’s hyphen-aware capitalization. It is not a reliable personal-name parser: e.g., abbreviations such as iOS, product brands, and exceptional surnames may need manual corrections after capitalization.

The earlier saved TRIM and IF proposals are used here as functions, not linked as if they were already published. Their behaviour should be checked in the specific Numbers app version when reviewing this combined example.

• Wrong source cell or circular reference: Keep raw input in A and the formula in B; if B refers to itself or a different table, revise the cell reference using the formula editor.
• Quoted text versus references: =PROPER(A2) transforms the contents of a cell; =PROPER("A2") transforms the two-character literal, not the cell’s contents.
• Not a whitespace cleaner: Character case changes do not trim leading spaces or collapse repeated internal spaces. Explicitly use a cleaning function when warranted.
• Case conversion is not identity matching: Inconsistent spelling, accents, alternate alphabets, and field formatting need their own review. Avoid asserting case rules for every language or older platform without native tests.
• Mixed types: Apple’s numeric example returns a string representation of the number; do not assume it stays a number or that formatting is preserved.
• Unexpected punctuation: Hyphens, numbers and punctuation are not removed. PROPER has special word-boundary rules that make it inappropriate for blindly standardizing product names or people.

PROPER-specific capitalization trap

Apple documents that a letter after most non-alphabetic characters is considered the start of a word, but apostrophes are an exception. Thus =PROPER("acME-lABS") is expected to return Acme-Labs. PROPER does not know that a brand may intentionally use mixed case. Treat examples involving curly versus straight apostrophes, local scripts, or acronyms as requiring native validation instead of inventing a universal rule.

Microsoft Excel provides PROPER with the same basic text-case goal and a text argument. For comparable simple Latin-letter input, a formula such as =PROPER(A2) has the same expected transformation. The apps are not interchangeable for table references: Numbers supports Names::A2 (or A2 inside the same table), whereas Excel worksheets use another notation. Test non-English text, word boundaries, source formatting and converted numeric values independently when migrating spreadsheets. Microsoft’s text-cleaning function overview and Apple documentation explain the respective use cases.

• TEXTAFTER
• TEXTBETWEEN
• Apple’s official LOWER reference and UPPER reference — companion functions; these are official docs, not falsely presented as already-published site guides.
• Apple’s official PROPER reference — documented word-boundary rules.

• Apple Numbers — function documentation
• cell-reference documentation
• function syntax guidance
• Apple’s official LOWER reference
• UPPER reference
• 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.