What is the TRIM formula in Spanish Google Sheets?

The TRIM formula in Spanish-locale Google Sheets is `=ESPACIOS()`. Google Sheets automatically localizes all 400+ built-in function names based on the spreadsheet's locale setting. When the locale is set to any Spanish-speaking country, TRIM becomes ESPACIOS. The function behavior is identical to TRIM: it removes leading and trailing spaces and collapses internal multi-space runs to a single space. Set your spreadsheet to España, México, Argentina, or any other Spanish locale and the translation happens automatically for all live formulas.

Does ESPACIOS remove non-breaking spaces (CHAR(160))?

No. ESPACIOS only strips Unicode U+0020 (the standard space character). Non-breaking spaces - U+00A0, called CHAR(160) in English locale or CARACTER(160) in Spanish locale - are a distinct code point and are explicitly excluded from TRIM/ESPACIOS behavior per the Unicode Standard. They appear frequently in ERP exports (SAP, Oracle) and in data copied from web browsers or PDFs. To remove them, use `=ESPACIOS(SUSTITUIR(A2, CARACTER(160), " "))`, which replaces each CHAR(160) with a regular space before ESPACIOS runs.

Do English formula names like TRIM work in a Spanish-locale Google Sheets?

No. If your spreadsheet locale is set to a Spanish-speaking country, entering `=TRIM(A2)` returns `#NAME?`. You must use `=ESPACIOS(A2)`. This applies to all 400+ localized function names - SUMIFS must be SUMAR.SI.CONJUNTO, VLOOKUP must be BUSCARV, and so on. Live formulas do translate automatically when you open a file in a different locale, but formula text stored as strings in documentation cells or comments does not translate and must be updated manually.

How do I detect CHAR(160) contamination across a multi-tab model in Spanish Google Sheets?

Use a helper column with `=LARGO(ESPACIOS(A2))<>LARGO(SUSTITUIR(A2, CARACTER(160), " "))`. This returns TRUE for any cell that contains a non-breaking space. Apply it as an ARRAYFORMULA across a full column - `=ARRAYFORMULA(LARGO(ESPACIOS('P&L_MX'!A2:A500))<>LARGO(SUSTITUIR('P&L_MX'!A2:A500, CARACTER(160), " ")))` - to generate a contamination flag for each entity name before you build cross-tab SUMAR.SI.CONJUNTO lookups against that data.

What other FP&A formulas change names in Spanish-locale Google Sheets?

The most impactful ones: SUMIFS becomes SUMAR.SI.CONJUNTO, VLOOKUP becomes BUSCARV, INDEX becomes INDICE, MATCH becomes COINCIDIR, IFERROR becomes SIERROR, SUBSTITUTE becomes SUSTITUIR, LEN becomes LARGO, LEFT becomes IZQUIERDA, RIGHT becomes DERECHA, and CHAR becomes CARACTER. IF becomes SI. Google Sheets handles the translation automatically in live formulas but not in formula text stored as strings, so any formula documentation or formula-as-text patterns in your model need manual translation when moving between locales.

TRIM Formula in Spanish Google Sheets: ESPACIOS Guide (2026)

That translation is automatic and invisible until it isn't. Paste a formula from an English-locale model into a Spanish-locale sheet and you get #NAME? instantly.

ESPACIOS vs. TRIM: What Changes and What Doesn't

Nothing changes functionally. =ESPACIOS(A2) strips leading and trailing spaces, then collapses any internal runs of multiple spaces down to a single space. Identical behavior to TRIM in any other locale.

What trips people up is what ESPACIOS doesn't strip: non-breaking spaces. The Unicode Consortium's character database defines U+00A0 as "NO-BREAK SPACE" and states explicitly that it "is not treated as whitespace by many text-processing functions." ESPACIOS follows that spec precisely. Feed it a string with CHAR(160) padding and the cell looks clean, but the invisible character stays, silently breaking every BUSCARV, SUMAR.SI.CONJUNTO, and string comparison downstream.

This is not a Spanish-locale quirk. TRIM in English has the same limitation. But it bites harder in Spanish-locale models because Spanish-language ERP and CRM exports - SAP, Oracle, and local accounting systems used across Latin America and Spain - are well-known for embedding CHAR(160) in text fields, particularly entity names, cost center labels, and SKU descriptions. In practice, any data copied from a web browser or pasted from a PDF carries a high risk of U+00A0 contamination, since HTML non-breaking spaces ( ) map directly to CHAR(160).

Where CHAR(160) Breaks Your Model

Here's a concrete example. You're building a P&L consolidation across 12 subsidiary tabs. Revenue by entity feeds from each subsidiary sheet into a Summary tab via SUMAR.SI.CONJUNTO:

=SUMAR.SI.CONJUNTO('P&L_MX'!C:C, 'P&L_MX'!B:B, ">="&Supuestos!$B$3, 'P&L_MX'!A:A, Summary!$A4)

Entity names in column A come from an SAP export. "Grupo Editorial Norte" in the source data looks identical to "Grupo Editorial Norte" in your Assumptions tab - same characters, same visual length. But the export wrapped the name in CHAR(160) padding. The SUMAR.SI.CONJUNTO returns zero. The P&L shows $0 for a $4.2M revenue line. You've just spent 45 minutes "fixing" cross-tab references that were never broken.

According to Google's Sheets function documentation (as of May 2026), ESPACIOS "removes all spaces from a text string except for single spaces between words." The operative word is spaces - Unicode code point U+0020. U+00A0 is a different code point, and ESPACIOS won't touch it.

Microsoft's Excel documentation documents the same behavior for TRIM, noting that the function "does not remove this nonbreaking space character" and recommending SUBSTITUTE as the fix - identical to the approach required in Spanish-locale Sheets.

The Fix: ESPACIOS + SUSTITUIR

Strip CHAR(160) before ESPACIOS touches the string:

=ESPACIOS(SUSTITUIR(A2, CARACTER(160), " "))

SUSTITUIR (SUBSTITUTE in English) replaces every non-breaking space with a regular space. ESPACIOS then collapses everything. Applied across a full entity name column in a consolidation model:

=ARRAYFORMULA(ESPACIOS(SUSTITUIR('P&L_MX'!A2:A500, CARACTER(160), " ")))

Run this as a helper column on each subsidiary tab, then point your SUMAR.SI.CONJUNTO at the helper column instead of the raw SAP export column. Revenue ties. Crisis over.

If your data comes from multiple sources with potentially different encoding issues, stack SUSTITUIR calls:

=ESPACIOS(SUSTITUIR(SUSTITUIR(A2, CARACTER(160), " "), CARACTER(9), " "))

CARACTER(9) is a tab character - another common stowaway in ERP and CSV exports.

Spanish Locale Formulas at a Glance

Google Sheets localizes all function names when the locale is set to a Spanish-speaking country. As of May 2026, this covers more than 400 built-in functions across 50+ supported locales. The ones FP&A analysts hit most often:

English	Spanish	Notes
TRIM	ESPACIOS	Strips U+0020 whitespace only
SUBSTITUTE	SUSTITUIR	Use with ESPACIOS for CHAR(160)
CHAR	CARACTER	Same code points, same behavior
SUMIFS	SUMAR.SI.CONJUNTO	Full multi-criteria support
VLOOKUP	BUSCARV	Works identically
INDEX	INDICE	Pair with COINCIDIR
MATCH	COINCIDIR
IFERROR	SIERROR
IF	SI
LEFT	IZQUIERDA
RIGHT	DERECHA
LEN	LARGO

One practical implication worth flagging: if you share a model between a Spanish-locale analyst and an English-locale analyst, live formulas translate automatically when opened. But formula text stored as strings - in documentation cells, validation notes, or comments - doesn't translate. Those need manual updates.

Automating the Audit

Tracking down CHAR(160) contamination across a 12-tab consolidation model by hand is tedious. A quick detection formula using LARGO (LEN):

=LARGO(ESPACIOS(A2)) <> LARGO(SUSTITUIR(A2, CARACTER(160), " "))

This returns TRUE for any cell containing a non-breaking space. Wrap in ARRAYFORMULA across your subsidiary tabs to generate a contamination map before you start building cross-tab lookups.

ModelMonkey can run this scan automatically - flag contaminated cells across a range, then write the corrected SUSTITUIR+ESPACIOS formula to a helper column. It works in Spanish-locale sheets natively, so the formulas it writes back use ESPACIOS, SUSTITUIR, and CARACTER rather than their English equivalents.