# Case-Sensitive and Case-Insensitive TRON Patterns

Source: https://www.tronvanity.io/blog/tron-vanity-case-sensitivity

Published: 2026-11-06

Updated: 2026-11-09

![Search mode versus address spelling. Exact mode: Matches requested capitalization; Flexible mode: Accepts configured case alternatives; Final address: Keep the exact spelling of the returned value.](https://www.tronvanity.io/images/blog/tron-vanity-case-sensitivity-diagram-v2.webp)

Search mode versus address spelling. Exact mode: Matches requested capitalization; Flexible mode: Accepts configured case alternatives; Final address: Keep the exact spelling of the returned value.

[Full-size diagram (SVG)](https://www.tronvanity.io/images/blog/tron-vanity-case-sensitivity-diagram-v2.svg)

[Diagram download (PNG)](https://www.tronvanity.io/images/blog/tron-vanity-case-sensitivity-diagram-v2.png)

Base58 distinguishes uppercase and lowercase characters. Ignoring case broadens pattern matching without changing the returned address.

## Uppercase and lowercase are different Base58 symbols

Base58 uses both cases but omits visually ambiguous characters: zero, uppercase O, uppercase I and lowercase l. Consequently, not every letter has two accepted case variants. An input containing an excluded symbol is not rescued by switching off case sensitivity.

For example, A and a are both valid symbols. Uppercase L is valid while lowercase l is not. Think of the input as symbols from a specific alphabet, not arbitrary text.


## Ignoring case changes the search comparison

Case-insensitive mode allows candidate patterns whose letters differ in case where valid. It can increase the set of acceptable results. Exact-case mode accepts only the requested spelling. Neither mode changes the fixed network marker or the checksum rules.

Do not edit the returned address to force your preferred capitalization. The generated string is the destination. Modifying a character changes the encoded value and may make the checksum invalid.


## Decide whether the spelling matters

Use exact case when the visual pattern must retain a particular form. If recognition is enough, case-insensitive matching can accept more outcomes. It still does not guarantee a completion time or make every leading pattern feasible.

Read [the prefix feasibility and difficulty guide](https://www.tronvanity.io/blog/tron-vanity-address-difficulty) for those limits. The [search walkthrough](https://www.tronvanity.io/blog/tron-vanity-search-guide) shows how to submit a request and handle its completed result.


## Explore the related mechanism

- [TRON Vanity Address Difficulty: Odds and Time](https://www.tronvanity.io/blog/tron-vanity-address-difficulty) — Longer patterns are harder to match. A search is probabilistic, so an average number of attempts is not a deadline.
- [TRON Vanity Search: Prefix and Suffix Guide](https://www.tronvanity.io/blog/tron-vanity-search-guide) — Choose one prefix or one suffix of up to eight Base58 characters. Use a short pattern first to verify the complete workflow.
- [Open the complete workflow guide](https://www.tronvanity.io/guide) to place these checks in order.
- [Open the address generator](https://www.tronvanity.io/) when you have chosen a compatible format and pattern.

## Sources

- [TRON developer documentation: accounts and keys](https://developers.tron.network/docs/account)



Editorial method: https://www.tronvanity.io/about#publication-method