# Line ending auditor

- Human page: https://happytails.ai/en/developer-tools/line-ending-auditor/
- Markdown: https://happytails.ai/en/developer-tools/line-ending-auditor.md
- Structured JSON: https://happytails.ai/agents/en/developer-tools/line-ending-auditor/index.json
- Visibility: public

## Tool capabilities

| Property | Value |
| --- | --- |
| Tool ID | `line-ending-auditor` |
| Category | developer-tools |
| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |
| Browser execution | Use the visible action or interactive controls. |
| Browser processing | Browser; see tool notes for network behavior. |
| HTTP API | Not callable through HTTP. |
| Browser-agent interface | run_current_tool |

### Implementation notes

Check up to 100 UTF-8 files, 16 MiB total. Normalization preserves the UTF-8 BOM and non-newline bytes. Other encodings and NUL bytes are rejected; original files remain unchanged.

### Inputs and settings

No free-text input is required. Use the file inputs and/or settings below.

Accepted browser files: `See implementation notes`. Multiple files are supported.

Browser file-input limit: 16777216 bytes in total. HTTP limits can differ.

| Setting | Meaning | Control type | Default | Constraints |
| --- | --- | --- | --- | --- |
| `action` | Action | select | "Audit only" | Allowed: Audit only, Normalize LF, Normalize CRLF, Normalize CR |

### Browser-agent workflow

1. Open the human page in a browser that supports WebMCP.
2. Discover the interface exposed by that page; use its actual schema.
3. Select files on the page first when the tool requires files.
4. Call `run_current_tool` with valid input and settings.
5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.

Calls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.

### Planning specification

Up to 100 valid UTF-8 files and 16 MiB total. UTF-8 BOMs are preserved; other Unicode encodings, invalid UTF-8 and NUL bytes are rejected. Blank lines and the presence or absence of the final line ending are preserved.

This describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.

### Complete machine-readable capability record

```json
{
  "id": "line-ending-auditor",
  "category": "developer-tools",
  "built": true,
  "requirements": "Up to 100 valid UTF-8 files and 16 MiB total. UTF-8 BOMs are preserved; other Unicode encodings, invalid UTF-8 and NUL bytes are rejected. Blank lines and the presence or absence of the final line ending are preserved.",
  "implementation": {
    "fields": [
      {
        "key": "action",
        "label": "Action",
        "value": "Audit only",
        "type": "select",
        "values": [
          "Audit only",
          "Normalize LF",
          "Normalize CRLF",
          "Normalize CR"
        ]
      }
    ],
    "files": true,
    "input": false,
    "multiple": true,
    "maxFileBytes": 16777216,
    "presentation": "metrics",
    "deferImagePreview": true,
    "note": "Check up to 100 UTF-8 files, 16 MiB total. Normalization preserves the UTF-8 BOM and non-newline bytes. Other encodings and NUL bytes are rejected; original files remain unchanged.",
    "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.",
      "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

Count CRLF, LF and CR line endings and normalize selected UTF-8 files without rewriting their other bytes.

How can we improve this tool?

Report a problem or share an idea.

Please leave out private information. Your message and the tool name go to our team via PostHog.

### How to use Line ending auditor

1. Choose the local file or files.
2. Review the action and limits, then run the inspection.
3. Check the result and download a separate output or report.

## Useful next steps

- [Byte order mark editor](https://happytails.ai/en/developer-tools/byte-order-mark-editor/) ([Markdown](https://happytails.ai/en/developer-tools/byte-order-mark-editor.md))

- [Binary file comparator](https://happytails.ai/en/developer-tools/binary-file-comparator/) ([Markdown](https://happytails.ai/en/developer-tools/binary-file-comparator.md))

- [File hash](https://happytails.ai/en/developer-tools/file-hash/) ([Markdown](https://happytails.ai/en/developer-tools/file-hash.md))

## Count endings before changing them

Audit the selected files to see CRLF, LF and CR counts separately. Mixed endings are reported per file.

### Choose one line-ending style

Normalize to LF, CRLF or CR. Only newline byte sequences change; text and an existing UTF-8 marker are preserved.

### Match numbered downloads to source files

The report maps each numbered result to the original selected filename. Audit-only mode creates a report without transformed files.