TL;DR: A1Z26 ignores case—A and a both equal 1. Normalize to uppercase mentally for counting, and expect converters to uppercase internally before mapping.
Case does not change numeric values
The cipher maps letter identity, not typography. Lowercase hello and uppercase HELLO yield 8 5 12 12 15. Mixed case HeLLo produces the same sequence because each character resolves to its letter regardless of caps lock.
Why tools uppercase internally
Software often normalizes input to uppercase before lookup tables run. This prevents duplicate table entries for a/A. You may paste lowercase and see uppercase echoed in a preview—that is display convention, not a different cipher.
Grading student work fairly
Accept correct number sequences even if students wrote input in lowercase. Deduct only when numbers are wrong, not when casing differs. Publish a rubric line: “Case ignored for A1Z26 scoring.”
When case matters outside A1Z26
Case-sensitive ciphers (ASCII codes, Base64, hex) are different systems. If an assignment mentions “case sensitive,” assume it is not plain A1Z26. Clarify with instructor before encoding.
Mixed-case brand names and usernames
Encode iPhone as 9 16 8 15 14 5 regardless of the camelCase display. Decode back to letters; restore original casing from context if the message is a proper noun.
Accessibility and screen readers
Screen readers announce case when spelling letter by letter. For visually impaired learners, consistent uppercase output from letterstonumbers.com reduces confusion during read-back.
Keyboard caps lock accidents
Caps lock does not alter A1Z26 results. It can alter passwords or login fields on other tabs—switch context carefully when multitasking during cipher labs.
Teaching normalization explicitly
Demonstrate one word in four case variants on the projector; show identical numbers. Students stop worrying about caps and focus on arithmetic of letter positions.
Export to documents that auto-capitalize
Word processors may title-case decoded sentences. Turn off auto-format for cipher homework or paste as plain text to preserve intentional mid-word caps from the original message.
Quick classroom demo script
Type “cipher” in lowercase, uppercase, and alternating case in the tool. Display three identical outputs. Five minutes of demo prevents twenty minutes of case-related questions later.
Normalization in software pipelines
Converters uppercase internally because letter identity drives the map, not typography. Mixed-case input HELLo still yields correct numbers.
Display previews may echo uppercase even when you typed lowercase—cosmetic only, not a different cipher.
Grading and rubric clarity
Accept correct numeric sequences regardless of input case. Deduct for wrong numbers, not lowercase letters in the source phrase.
Publish one syllabus line: Case ignored for A1Z26 scoring. Prevents appeal emails.
When case-sensitive systems differ
ASCII, Base64, and hex encodings are not A1Z26. Assignment headers mentioning case sensitivity usually reference those systems instead.
Clarify with instructor before encoding begins on ambiguous cross-curricular projects combining CS and English units.
Proper nouns after decode
Decode returns uppercase letters; restore original brand casing from context—iPhone stays camelCase in final essay even if cipher output is IPHONE.
Accessibility read-back consistency
Screen readers announce case when spelling aloud. Consistent uppercase converter output on https://letterstonumbers.com/ reduces confusion during accessible testing accommodations.
Why eBay and iPad survive case folding
Brand spellings tempt students to treat capitals as data. eBay starts with a lowercase e and a capital B. iPad capitalizes the second letter. A1Z26 does not care. eBay encodes as 5 2 1 25. iPad encodes as 9 16 1 4. The same digits appear if the words are shouted as EBAY and IPAD. A grading key that rejects the lowercase version is grading typing, not the cipher.
Show the pair on a projector in three lines: ebay, EBAY, and eBaY. Run them one after another. The number rows match. Then type the Turkish word ISTANBUL in all capitals and in the dotted-i lowercase form if the keyboard can produce it. Many converters fold only the English i. If the dotted capital fails to map, the honest classroom rule is: transliterate to the 26 English letters first, then encode. Write that sentence on the rubric so a student with a bilingual keyboard is not marked wrong for a character the tool never claimed to understand.
Caps-lock story from a shared lab keyboard
A lab keyboard with caps lock stuck will turn a careful lowercase sentence into a shout. The numbers should not change. If they do, the student probably typed a digit row by accident while chasing the lock key, or the tool echoed an error glyph that got copied into the answer. Decode the first word only. If HELLO still returns 8 5 12 12 15, caps lock is innocent and the later mismatch is a different letter.
Ask the student to retype just the mismatched word with the lock off and with it on. Identical output ends the argument. Different output means a non-letter sneaked in, often a superscript from a copied worksheet. That is a paste problem, not a case problem, and it should be fixed by retyping the word rather than by “correcting” the alphabet.
Grading eBay without punishing the lowercase e
Put 5 2 1 25 on the answer key and accept ebay, EBAY, and eBaY as the same response. Add a note for the marker: “case is not an error.” The note prevents a substitute teacher from docking points on Friday because the worksheet model was typed in capitals. Read one mixed-case paper aloud and show the numbers. The room should hear that the lowercase e still means 5.
If a paper shows 5 2 1 25 for eBay and then a different row for EBAY, the student has invented a rule. Sit with that paper only. Ask them to point at the letter they think changed. Usually they point at B and say the capital “feels like a bigger number.” The correction is one sentence: capitals are shape, not position. Then have them encode iPad and IPAD on the same line and watch the rows match.
