Language Detector

Language Detector before-and-after example: Source text = This is a short English sentence. Language Detector expected result: The sample is expected to be labelled English with a heuristic confidence score and reason.

For Language Detector, text is handled as a JavaScript string; the operation does not normalize Unicode forms, so visually identical composed and decomposed text can remain different.

For Language Detector, line operations split on LF or CRLF. For Language Detector, whitespace is preserved unless the named transformation explicitly trims, removes, or replaces it.

For Language Detector, the operation preserves letter case unless it is specifically a case-conversion or lowercase-counting operation. For Language Detector, duplicate input is retained unless the named operation explicitly removes or reports duplicate lines.

For Language Detector, the operation does not sort input; source order is preserved except when the page explicitly reverses text or lines.

For Language Detector, empty input can produce an empty result, a zero count, or the page’s validation message. For Language Detector, the operation does not repair malformed data beyond its documented transformation.

For Language Detector, the transformation runs in the current browser session and the page code does not submit the text to this site’s server. Language Detector reads and processes the supplied values in the current browser and does not submit them to an application endpoint. Browser extensions, device security and any manual sharing or download from Language Detector remain outside the tool’s control.

To verify Language Detector, reproduce its worked example and compare the displayed or downloaded language estimate with the stated expected result. When Language Detector returns a file, open the download and inspect every affected page or image. After using Language Detector, you may also find these tools useful: text-translator, word-counter, case-converter.