Text File Check

TEXT FILE CHECK

Check a text file

Inspect text encoding, BOM markers, line endings, unusual control characters, empty files, and decoding problems directly in your browser.

Drop your text file here
or
TXT · LOG · MD · INI · CFG · CONF · plain text
UTF-8 and BOM-marked UTF-16 text are decoded locally in your browser. The selected file is not uploaded to ARADURU.
No upload Designed for local processing No account Start without signing up Clear results Understand what went wrong
WHEN TO USE THIS CHECK

Text file looks garbled, inconsistent, or unreadable?

Start with encoding and file-side structure. ARADURU checks how the selected bytes decode, which line endings are used, and whether the file contains binary-looking characters.

The text will not decode correctlyCheck UTF-8 or BOM-marked UTF-16 decoding before assuming the text was permanently damaged.
Line endings are mixedDetect LF, CRLF, CR, or mixed line-ending styles that can affect scripts and developer tools.
The file may contain binary dataEmbedded NUL and unusual control characters can indicate that the file is not ordinary plain text.
The file is empty or unexpectedly shortConfirm whether the selected text target contains any readable content before troubleshooting the application.
Check my text file ↑ No account. The selected text is decoded locally in your browser.
WHAT ARADURU CHECKS

Text checks that focus on portability

The Text File Doctor checks byte-to-text decoding and practical text-file boundaries. It does not pretend to understand every programming language or application format.

01

Encoding and BOM

Check UTF-8, UTF-8 BOM, UTF-16 LE BOM, and UTF-16 BE BOM decoding for the complete selected file.

02

Line-ending profile

Count text lines and distinguish LF, CRLF, CR, mixed endings, or text with no line-ending sequence.

03

Binary-looking characters

Look for embedded NUL and unusual low control characters that can make an ordinary-text interpretation unreliable.

WHAT THIS DOES NOT GUARANTEE

Readable text is not the same as valid application syntax.

A text file can decode cleanly and still contain invalid source code, malformed configuration, wrong delimiters, unsupported markup, application-specific syntax errors, or the wrong human language.

  1. Keep the original. Normalize or edit a copy when the text matters.
  2. Check the application syntax separately. Encoding health cannot validate source code or configuration rules.
  3. Use Compatibility Check. Review file-side portability separately from application support.
  4. Use Upload Check. Compare file size, filename, and allowed-type rules before submission.
COMMON TEXT PROBLEMS

Check a specific text-file problem

Text file looks garbled → Text file encoding problem → Mixed line endings →
RELATED TOOLS

Need a different file check?

Open File Check → Open Compatibility Check → Check upload requirements → Check a data file → Check an image file → Check a PDF file → Browse all tools →