XML Base64 variants

게시

이 가이드에서

This standards reference on Base64Encoding explains xml in plain language for developers and everyday users.

Everything important stays private: try the matching converter or tool in your browser — files and tokens are not uploaded.

Read the full English article below for code samples and edge cases, or switch language anytime from the menu. We keep expanding translations from real user feedback.

다음으로 이 비공개 도구를 써 보세요

Some XML schemas need opaque binary identifiers that remain valid as NMTOKEN or Name values. Instead of + and /, they swap the last two Base64 alphabet characters:

Variant Chars 62 / 63 Padding Typical use
XML name token . - none NMTOKEN / NMTOKENS attributes
XML identifier _ : none XML Name / ID-like values

Both omit padding. They are rare compared with RFC 4648 and Base64URL, but appear in niche enterprise XML and legacy interoperability specs.

How to work with them here

  1. Paste a suspicious value into the Base64 standard detector.
  2. Convert to standard Base64 with normalization.
  3. Or decode directly on Base64 decode after selecting the matching XML standard.

If your value contains - and _ only, it is more often Base64URL (JWT, OAuth) than an XML variant.

자주 묻는 질문

Does this page upload my data?

No. Articles are static. Linked tools run locally in your browser unless a feature explicitly needs a network relay.

Can I request a translation or a new tool?

Yes — use the private feedback form. We prioritize what users ask for across languages.

What is the fastest way to try xml?

Open the homepage Base64 converter or the related tools linked on this page and paste a sample.

관련 도구 및 가이드

댓글 (0)

“XML Base64 variants”에 대한 질문, 아이디어, 버그가 있으신가요? 댓글을 남기거나 도구를 평가하거나 다른 사람에게 답글을 달아 주세요.

아직 댓글이 없습니다. 첫 번째로 의견을 남겨 주세요!

댓글 남기기

이 도구 평가:
Esc
↑ ↓ 이동↵ 열기Esc 닫기