UUID with Internal Space – Why Whitespace Inside UUID Fails

Local only

Contrast supported surrounding-whitespace trimming with unsupported whitespace inside UUID text.

37 chars · 1 line

Needs attention

Invalid UUID format

UUID input normalization

Are spaces inside a UUID allowed?

VetaTool trims whitespace around a UUID, but whitespace inserted between hexadecimal characters changes the canonical 8-4-4-4-12 text. Internal spaces are therefore rejected as an invalid UUID format. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Canonical 8-4-4-4-12 UUID validation
  • UUID version inspection
  • RFC 4122 variant checking
  • Nil UUID recognition
  • Uppercase hexadecimal support
  • Browser-local validation

Steps

  1. Inspect the UUID for spaces, tabs, or line breaks inside the 36-character canonical value.
  2. Remove accidental internal whitespace only when you know it is copy/paste noise.
  3. Validate the restored canonical UUID text.

trim does not normalize internal characters

JavaScript string trim removes whitespace at the beginning and end of the input. It does not remove whitespace in the middle of a string.

That distinction prevents the validator from silently rewriting identifier characters beyond a predictable outer trim step.

Internal space example

One space appears inside the final UUID group.

UUID input

550e8400-e29b-41d4-a716-44665544 0000

Validation result

Invalid UUID format

Common questions

Frequently asked questions

Why did the whitespace page validate successfully?

That page places whitespace only before and after the UUID, where trim removes it. Internal whitespace remains part of the value and fails the pattern.

Does VetaTool automatically remove internal spaces?

No. The validator deliberately avoids rewriting internal UUID characters.

Debugging a specific UUID issue? Browse UUID troubleshooting.