# Strict explicit Unicode and Latin1 byte transcoder

Build-time release reference. Runtime readiness, deployment, payment settlement and external indexing are not evaluated here. Prices are proposed; this file cannot authorize execution or payment.

WHEN TO USE: Convert caller-supplied Base64 text-file bytes between explicit UTF-8, UTF-16LE, UTF-16BE and reversible Latin1 byte mapping with strict BOM rules. Rejects malformed sequences and unrepresentable scalars without replacements. No charset detection, Windows-1252 aliases, normalization, newline conversion or plaintext echo.

Release: 0.29.0. Built: 2026-10-06T15:38:00Z.

## Choose for
- Know both source and target encoding and explicit initial-BOM policy

## Outside this profile
- Guessing encodings, repairing mojibake, lossy replacement, newline conversion or Unicode normalization
- Windows-1252, ASCII aliases, ISO-8859-1 WHATWG label handling or arbitrary legacy code pages
- Blind transcoding of fixed byte-column files whose layout depends on original encoding
- Extracting archives, writing files, uploading, publishing, or changing external state

Proposed nominal USD 0.003 per successful call; payer fees excluded. No verified runtime availability.

- [Exact release contract](/reference/services/text-bytes-transcode.json)
- [Input schema](/reference/schemas/text-bytes-transcode.input.json)
- [Output schema](/reference/schemas/text-bytes-transcode.output.json)
- [Fixed example](/reference/examples/text-bytes-transcode.json)
- [Complete HTML reference](/discover/tools/text-bytes-transcode)