About

ASCII uppercase-to-lowercase conversion maps each character in the range A - Z (decimal 65 - 90) to its lowercase counterpart a - z (decimal 97 - 122) by adding an offset of +32 to the code point. This tool processes raw ASCII and extended character sequences. It preserves digits, punctuation, whitespace, and all non-alphabetic code points without modification. Incorrect case handling in data pipelines causes silent failures: duplicate database keys, broken string comparisons, and mismatched API parameters that return empty results instead of errors.

This converter operates entirely in-browser with zero server round-trips. It reports exact conversion statistics so you can verify how many characters were actually transformed. Note: this tool targets the ASCII subset. Characters outside the Basic Latin block (accented letters like É or Ö) are passed through unchanged. For full Unicode case folding, a locale-aware implementation using ICU rules would be required.

Formulas

The ASCII lowercase conversion applies a fixed arithmetic offset to each uppercase character code point:

c_lower = c_upper + 32

The conditional rule governing the transformation:

{

c + 32 if 65 ≤ c ≤ 90c otherwise

Where c is the decimal ASCII code point of the input character. The offset 32 equals 0x20 in hexadecimal, which is the fixed distance between uppercase and lowercase Latin letters in the ASCII table. This is equivalent to setting bit 5 (zero-indexed) of the byte: c_lower = c_upper | 0x20. The bitwise OR approach works because uppercase ASCII letters have bit 5 cleared and lowercase letters have it set.

Reference Data

Character	Uppercase Code	Lowercase	Lowercase Code	Offset
A → a	65	a	97	+32
B → b	66	b	98	+32
C → c	67	c	99	+32
D → d	68	d	100	+32
E → e	69	e	101	+32
F → f	70	f	102	+32
G → g	71	g	103	+32
H → h	72	h	104	+32
I → i	73	i	105	+32
J → j	74	j	106	+32
K → k	75	k	107	+32
L → l	76	l	108	+32
M → m	77	m	109	+32
N → n	78	n	110	+32
O → o	79	o	111	+32
P → p	80	p	112	+32
Q → q	81	q	113	+32
R → r	82	r	114	+32
S → s	83	s	115	+32
T → t	84	t	116	+32
U → u	85	u	117	+32
V → v	86	v	118	+32
W → w	87	w	119	+32
X → x	88	x	120	+32
Y → y	89	y	121	+32
Z → z	90	z	122	+32
0-9	48 - 57	0-9	48 - 57	0
Space	32	Space	32	0
! @ # $ %	33 - 37	! @ # $ %	33 - 37	0
Newline (LF)	10	Newline	10	0

Frequently Asked Questions

Any character with a code point outside the range 65 - 90 passes through unchanged. This includes digits (0 - 9), punctuation, whitespace, newlines, and extended ASCII characters above 127. The tool only modifies the 26 uppercase Latin letters defined in the ASCII standard.

No. This converter targets the strict ASCII subset (code points 0 - 127). Accented characters like É (code point 201) fall outside this range and are passed through unmodified. Full Unicode case mapping requires locale-aware rules defined in the Unicode Common Locale Data Repository (CLDR), which is a fundamentally different algorithm.

The ASCII table was designed in the 1960s with bit-level manipulation in mind. Uppercase letters start at 0x41 and lowercase at 0x61. The difference of 0x20 (32 decimal) means case conversion is a single-bit toggle: bit 5 of the byte. Setting bit 5 converts to lowercase. Clearing it converts to uppercase. This made hardware implementations trivial on early systems.

The tool returns the text unchanged and reports 0 characters converted. Lowercase letters (97 - 122) do not fall within the uppercase range condition, so no offset is applied. The statistics panel will show the breakdown so you can confirm no transformation occurred.

The tool enforces a soft limit of 500,000 characters. Beyond this threshold, browser memory and DOM rendering become bottlenecks. A warning toast appears if you exceed the limit. For bulk processing of files larger than 500 KB, a command-line tool or streaming processor would be more appropriate.

Partially. This tool handles the case conversion step, but slug normalization also requires replacing spaces with hyphens, stripping non-alphanumeric characters, and collapsing consecutive separators. Use this tool for the case step, then apply additional formatting rules. Also note that database collation settings (e.g., utf8_general_ci in MySQL) may already perform case-insensitive comparison, making pre-conversion unnecessary.