Fix Rust base64 Invalid symbol 10 offset errors
In Rust base64 decoding, symbol 10 is byte 0x0A: a line feed copied into the encoded value.
Read guideGuides
Developer guides
Short, practical notes for common JSON, encoding, time, UUID, and text cleanup problems.
JSON troubleshooting
Fix, format, and validate JSON with context.
Fix Rust base64 Invalid symbol 61 padding errors
In Rust base64 decoding, symbol 61 is byte 0x3D, the equals sign used for padding.
Read guideAmpersand in URL query parameters
An ampersand separates query parameters. Encode it as %26 when the ampersand is part of the value.
Read guideWhy plus means space in form-encoded URLs
In application/x-www-form-urlencoded data, a plus sign can decode as a space. Encode a literal plus as %2B.
Read guideBase64 newline issue and invalid symbol 10
A newline pasted into a Base64 value can look invisible, but strict decoders may reject it as a real character.
Read guideURL space encoding: %20 vs plus
%20 is the normal encoded space in a URL. A plus sign only means space in form-style query values.
Read guideRegex match everything between brackets
The right bracket regex depends on whether the text has one pair, many pairs, or nested brackets.
Read guideUser agent string meaning explained
A user agent string is a clue about the client making a request, not proof of what that client really is.
Read guideJSON.stringify escape quotes problem
JSON.stringify adds backslashes before quotes when JSON text is being stored inside another string.
Read guideRobots.txt block all except one page
robots.txt controls crawling. It is the wrong tool if your real goal is to remove pages from search results.
Read guideURL decode not working fix
URL decoding goes wrong when percent escapes are broken, plus signs are misread, or the value was encoded more than once.
Read guideJSON format error line 1 column 1
A JSON error at line 1 column 1 means the parser failed before it found a real JSON value.
Read guideMD5 vs SHA-256: which is safer?
SHA-256 is the safer choice for checksums and integrity checks. MD5 is old enough that it should not guard security decisions.
Read guideFix a JSON unexpected token error
Unexpected token errors usually mean the parser found a character that is not allowed at that exact point in the JSON.
Read guideFix unexpected token o in JSON at position 1
Unexpected token o at position 1 usually means JSON.parse received an object or [object Object] text instead of a valid JSON string.
Read guideFix trailing commas in JSON
JSON does not allow a comma after the final item in an object or array, even though many JavaScript examples do.
Read guideMinify JSON without changing the data
JSON minifying removes whitespace and line breaks after the input parses successfully.
Read guideFormat escaped JSON from logs
Escaped JSON is JSON stored inside a string, often with backslashes before quotes and newline characters.
Read guideConvert a JSON string into readable JSON
A JSON string can contain another JSON value as text. To inspect it, decode the string first, then format the inner value.
Read guideValidate JSON before you send it
A quick validation pass catches syntax problems before a payload reaches an API, config loader, or test runner.
Read guideFormat an API response for debugging
Raw API responses are often minified. Formatting gives each object and array enough space to inspect quickly.
Read guidePretty print JSON for easier reading
Pretty printing turns compact JSON into indented text so nested structures are easier to review.
Read guideConvert URL spaces to %20
Spaces are not safe inside URLs. Percent-encoding changes each space to %20 so the link can travel cleanly through browsers, APIs, and logs.
Read guideEncode spaces in a URL
Encoding a space is simple; choosing the right part of the URL to encode is the detail that prevents broken links.
Read guideFix a URL with spaces
A URL with literal spaces can look harmless in a note but fail when it is copied into an API request, redirect field, or command line.
Read guideURL encode vs decode
Encoding prepares text for a URL. Decoding turns percent-encoded text back into something humans can read.
Read guideFix a Base64 invalid character error
Base64 decoding usually fails because the input contains extra text, a URL-safe alphabet, missing padding, or characters that are not part of standard Base64.
Read guideFix Base64 invalid padding and symbol 61 errors
Base64 padding errors come from a length mismatch, misplaced equals signs, copied wrappers, Base64URL values, or a decoder mode that does not match the source.
Read guideURL-safe Base64 vs standard Base64
URL-safe Base64 is a small variation that avoids characters with special meaning in URLs. That difference matters when you paste values into a standard decoder.
Read guideUnix timestamp seconds vs milliseconds
The same date can be written as Unix seconds or Unix milliseconds. Mixing the two is one of the fastest ways to get a date that looks wildly wrong.
Read guideConvert a Unix timestamp to a date
A Unix timestamp is compact and useful for machines, but a readable date is faster when you are debugging logs, API responses, and database rows.
Read guideUUID v4 vs UUID v7
UUID v4 is random. UUID v7 includes time information, so newly generated IDs sort more naturally by creation time.
Read guideGenerate UUIDs for testing
Fresh UUIDs are handy when you need realistic IDs for fixtures, API examples, seed data, or manual testing.
Read guidecamelCase vs snake_case
camelCase and snake_case are both common naming styles. The right choice usually depends on the language, API, or project convention you are working inside.
Read guideConvert text to kebab-case
kebab-case joins lowercase words with hyphens. It is useful for slugs, filenames, routes, and readable identifiers.
Read guideDecode a Base64URL string
Base64URL looks almost like Base64, but it uses URL-safe characters and often drops padding. Normalizing it first avoids many decode errors.
Read guideJSON escape vs unescape
Escaped JSON is usually text inside another JSON string. Unescaping removes one string layer so the real value can be formatted or validated.
Read guideURL encode a query parameter
Query parameters break when values contain spaces, ampersands, equals signs, or nested URLs. Encoding the value keeps the full parameter intact.
Read guideUnix timestamp in JavaScript
JavaScript Date.now returns milliseconds, while many APIs expect Unix seconds. The mismatch is a common source of wrong dates.
Read guideBase64 decode UTF-8 text
Base64 can represent UTF-8 text, but decoded bytes are not always readable characters. Check the original encoding before trusting the output.
Read guide