logo
search
Others

Fix Microsoft Lists Number Column Custom Format Showing Encoded Characters

Rana GarciaRana Garcia Sep 28, 2026 869 views

Question details

The user's Microsoft Lists number columns are displaying URL-encoded strings instead of spaces when custom formatting is applied.

Fix Microsoft Lists Number Column Custom Format Showing Encoded Characters
Product
Microsoft Lists
Device & OS
not provided
Scenario
Applying custom formatting to a Number column that includes a symbol with a space, or when a setting is deleted.
Observed behavior
The column displays incorrectly encoded expressions, such as "%252520%2520%20", rather than the intended space character.
Before you start

Verify that the encoded characters appear consistently across different web browsers or in incognito mode to confirm the issue is not caused by local browser caching.

Solution 1Recommended

Report the Defect via Microsoft 365 Admin Center

Because this is a known product-side defect affecting multiple tenants in Microsoft Lists and SharePoint Online, the issue requires a backend fix from Microsoft's development team.

Community moderators and end-users do not have the necessary backend access to patch rendering bugs. Resolving this issue requires collecting backend logs and opening an official service request.

1
Document the issue

Take clear screenshots of the encoded characters in your list and write down the exact steps to reproduce the formatting error, including the custom format formula used.

2
Contact your IT administrator

Reach out to your organization's Microsoft 365 administrator, as standard users typically lack the permissions to submit direct service requests to Microsoft.

3
Open a service request

Have the administrator log into the Microsoft 365 admin center, navigate to the Support tab, and create a new support ticket including your tenant details and the screenshots.

Report the Defect via Microsoft 365 Admin Center
Check Service Health: Ask your admin to monitor the Microsoft 365 Service Health dashboard to see if Microsoft has formally acknowledged this defect as an active widespread incident.
Free Microsoft Office alternative

Manage Tabular Data Flawlessly with WPS Spreadsheet

Tired of unpredictable cloud formatting bugs interrupting your workflow? Switch to WPS Office for a stable, offline-capable, and completely free alternative to manage tabular data, track lists, and format custom numbers precisely how you want them.

  1. 1. Download and Install WPS Office: Visit the official WPS Office website and install the lightweight software on your device.
  2. 2. Export Your List: In Microsoft Lists, select the 'Export' option to download your current list data as an Excel or CSV file.
  3. 3. Manage Data Without Errors: Open the exported file in WPS Spreadsheet to customize your number formatting securely without running into cloud-based encoding bugs.
Avoid cloud-sync rendering errors with a highly stable desktop spreadsheet environment.Fully compatible with Microsoft Excel (.xlsx, .xls, .csv) formats to migrate your lists easily.Completely free, lightweight, and fast to launch on Windows, Mac, and Linux.Familiar tabbed interface means zero learning curve for users switching from Microsoft Office.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Microsoft List show '%252520' instead of a space?

This happens due to a backend rendering bug in Microsoft Lists and SharePoint Online. The system improperly applies multiple layers of URL encoding to the space character within your custom number formatting formula.

Can I fix the encoded characters by changing my web browser?

No, changing browsers or clearing your cache will not resolve this. It is a verified server-side product defect that persists across all web browsers, operating systems, and even different Microsoft 365 environments.

How do I check if Microsoft is actively fixing this Lists formatting bug?

Your IT administrator can log into the Microsoft 365 admin center and check the Service Health dashboard. If Microsoft acknowledges the bug, it will be posted there with updates on the repair status.