Base64URL in serverless handlers: incident playbook

TL;DR: Validate locally, fix the first real error, validate again (no upload).

Handle Base64URL in serverless handlers: incident playbook with a repeatable Base64URL workflow: normalize alphabet, fix padding, decode locally, and validate.

Base64URL quick map

RuleBase64Base64URL
Alphabet+, /-, _
PaddingOften has =Often omits =
Typical useGeneral binary transportURLs, JWT segments

Focus for this query

  • Normalize alphabet ('-'/'_' vs '+'/'/').
  • Add or remove '=' padding based on your target format.
  • Validate with local tools before passing payload to your app.

Safe decode workflow

  1. Remove whitespace/newlines.
  2. Normalize alphabet: -→+, _→/.
  3. Add padding so length % 4 == 0.
  4. Decode locally and validate output shape (JSON/text/binary).

Runtime snippet (generic)

function base64urlToBase64(input) {
  const s = String(input || '').replace(/\s+/g, '').replace(/-/g, '+').replace(/_/g, '/');
  return s + '='.repeat((4 - (s.length % 4)) % 4);
}

const b64 = base64urlToBase64(token);
const bytes = Uint8Array.from(atob(b64), (c) => c.charCodeAt(0));
const text = new TextDecoder().decode(bytes);
console.log(text);

Frequent failures

Privacy guardrail

Base64/Base64URL strings can still contain secrets. Decode locally, redact sensitive fields, and only then share snippets.

FAQ

Is anything uploaded to a server? No. All processing happens locally in your browser. Files are never uploaded.

What is the recommended workflow? Validate the input, fix the first real issue, validate again, then export/convert. This avoids compounding errors.

Next steps
Related by intent
Convert Base64URL to Base64 (and back) without uploading Base64URL vs Base64: differences and safe conversion Base64URL missing padding: how to normalize '=' safely Base64URL decoded output won't parse as JSON: checklist
Privacy & Security
All processing happens locally in your browser. Files are never uploaded.

Related by intent

Closest pages and hubs to accelerate crawl discovery and first impressions.

First impression poolImpression seed hubIntent hub: runbooksTopic: base64urlRelated: winner compare node xml reference to entity must end with semicolon compatibility incident respoRelated: winner live 1 base64url vs base64 incident response securityRelated: winner compare ruby xml repeated elements arrays reliability incident responseRelated: winner compare node xml reference to entity must end with semicolon performance incident respons

First Impression Acceleration

Pages prioritized for first search impressions with fresh crawl/indexing signals.

Open first-impression pool
neighbor csharp go json cannot unmarshal array into field neighbor php go json cannot unmarshal string into field paneighbor csharp go json cannot unmarshal string into fieldneighbor php go json cannot unmarshal string into field usneighbor python go json cannot unmarshal string into fieldneighbor php go json cannot unmarshal string into field paneighbor csharp go json cannot unmarshal array into field neighbor php go json cannot unmarshal string into field usneighbor csharp go json cannot unmarshal string into fieldneighbor php go json cannot unmarshal string into field usneighbor java go json cannot unmarshal string into field pneighbor php winner csharp csharp newtonsoft error convertneighbor csharp go json cannot unmarshal array into field neighbor php go json cannot unmarshal string into field toneighbor csharp go json cannot unmarshal array into field neighbor php go json cannot unmarshal array into field pay