Byte order mark editor
Open Byte order mark editor on Happytails.ai. This view has the same page content and links, with explicit tool capabilities. Read the processing notes before using a tool.
Tool capabilities
{
"id": "byte-order-mark-editor",
"category": "developer-tools",
"built": true,
"requirements": "One file up to 256 MiB. Adding a marker validates the selected UTF-8, UTF-16 or UTF-32 encoding. Removing a marker strips only a recognized leading marker. No encoding conversion is performed.",
"implementation": {
"fields": [
{
"key": "action",
"label": "Action",
"value": "Inspect",
"type": "select",
"values": [
"Inspect",
"Add marker",
"Remove marker"
]
},
{
"key": "encoding",
"label": "Encoding to validate when adding",
"value": "UTF-8",
"type": "select",
"values": [
"UTF-8",
"UTF-16LE",
"UTF-16BE",
"UTF-32LE",
"UTF-32BE"
]
}
],
"files": true,
"input": false,
"multiple": false,
"maxFileBytes": 268435456,
"presentation": "metrics",
"deferImagePreview": true,
"note": "Inspect, add or remove a leading encoding marker. Adding validates the selected encoding; this does not transcode the payload. Maximum 256 MiB.",
"experience": {
"automatic": false,
"single": false,
"inputMaxLength": 1000000,
"inputMode": "text",
"label": "Your text",
"placeholder": "Type or paste your input…",
"help": "Up to 1,000,000 characters. Review the settings before running.",
"helpParts": [
"Up to 1,000,000 characters.",
"Review the settings before running."
],
"action": null
},
"mode": "explicit",
"interactive": false
},
"execution": "Browser interface",
"api": null,
"browser_agent": {
"supported": true,
"name": "run_current_tool",
"discovery": "WebMCP on the human page in a supporting browser",
"verification": "See audit/API-AUDIT.md; availability is not verification"
}
}Page guide
Inspect, add or remove a UTF byte order mark without changing the encoded payload.
How to use Byte order mark editor
- Choose the local file or files.
- Review the action and limits, then run the inspection.
- Check the result and download a separate output or report.
Useful next steps
Inspect the leading bytes
Choose a local file and inspect the detected marker. A missing marker does not identify the file encoding.
Add or remove explicitly
Choose the action. Adding validates the payload against the selected encoding; conflicting markers and invalid code units are rejected.
Keep the original
Download a new binary file. Every byte after the marker is preserved, and the source is never modified.