Guide

Litecoin address formats explained: legacy, SegWit, Bech32, and MWEB

Your address format determines your fees, privacy, and compatibility

If you have been using Litecoin for more than a year, you have probably noticed that not all LTC addresses look the same. Some start with L, some with M, some with ltc1q, and the newest ones start with ltc1p. There are also MWEB stealth addresses that look nothing like any of the above. These are not cosmetic differences. The prefix on your address tells you which cryptographic scheme secures your coins, how much you pay in transaction fees, and whether your wallet supports the latest protocol upgrades.

Most users never think about this. They use whatever address their wallet hands them, and that is how people end up paying 3x more in fees than necessary or accidentally sending LTC to a Bitcoin address and spending a weekend sweating over whether their coins are gone forever. This guide breaks down every Litecoin address format in use today, explains the real-world cost differences, and tells you exactly which format you should be using in 2026.

The five Litecoin address formats

L-addresses: legacy P2PKH

L-addresses are the original Litecoin address format, inherited from Bitcoin's P2PKH (Pay-to-Public-Key-Hash) scheme. Every address starts with a capital L, followed by 33 characters of base58-encoded data. Example: LM2WMpR1Rp6j3Sa59cMXMs1SPzj9eXpGc1

These addresses have been around since Litecoin launched in 2011. They work with every wallet, every exchange, and every service that has ever supported LTC. That universal compatibility is their only advantage. On the cost side, L-address transactions produce the largest data footprint on the blockchain because they use uncompressed signature encoding. Every byte costs you satoshis in fees. When the network is busy, the difference between an L-address transaction and an ltc1q transaction can be 40-60% in fees.

If your wallet still gives you L-addresses by default, it is either very old software or the developer stopped maintaining it. There is no technical reason to use L-addresses in 2026 unless you are interacting with ancient infrastructure that has not been updated since 2017.

M-addresses: P2SH (SegWit compatible)

M-addresses use the P2SH (Pay-to-Script-Hash) format and start with the letter M. Example: MJKbQ3bGFZx5gJnq5XkY5z3Kce2n6xPvSB

These became popular in 2017-2018 when Segregated Witness (SegWit) was activated on Litecoin. M-addresses wrap a SegWit script inside a legacy-compatible P2SH envelope. Think of it as SegWit wearing a disguise so that older wallets that do not understand SegWit can still send to these addresses without breaking. The transaction data is smaller than L-addresses because witness data is separated and discounted, but the P2SH wrapping adds overhead compared to native SegWit.

M-addresses were the transitional format. They solved the immediate problem of letting people use SegWit while the ecosystem caught up. By 2026, the ecosystem has caught up. Every major wallet and exchange supports native SegWit (ltc1q). M-addresses still work fine, but you are paying a fee premium over native SegWit for compatibility you no longer need.

ltc1q addresses: native SegWit (Bech32) — the recommended standard

ltc1q addresses use the Bech32 encoding format and are the native SegWit implementation for Litecoin. Example: ltc1qw508d6qejxtdg4y5r3zarvary0c5xw7kgmn4n9

These addresses are lowercase only, use a limited character set (no ambiguous characters like 0/O or l/1), and include a built-in checksum that catches typos before you send. If you mistype a single character, the address will be rejected as invalid instead of silently sending your LTC to a wrong (and possibly nonexistent) address. This error-detection alone has saved users an untold amount of money.

Transaction fees with ltc1q addresses are the lowest of any standard format. The witness data discount applies fully, and there is no P2SH wrapping overhead. On average, an ltc1q transaction is 30-45% cheaper than an equivalent L-address transaction and 10-15% cheaper than an M-address transaction. At current fee levels, the absolute difference is small (fractions of a cent), but it compounds over hundreds of transactions — and during high-traffic periods like halving events, the difference becomes meaningful. Check real-time fee comparisons on our fee tracker.

Every major wallet supports ltc1q: Litecoin Core, Electrum-LTC, Exodus, Trust Wallet, Ledger, Trezor, Tangem. Every major exchange supports sending to and withdrawing to ltc1q addresses. There is no reason not to use this format in 2026.

ltc1p addresses: Taproot (Bech32m)

ltc1p addresses use the Bech32m encoding (an improved version of Bech32 that fixes a theoretical weakness in error detection) and correspond to Taproot outputs (P2TR). Example: ltc1p5cyxnuxmeuwuvkwfem96lqzszee2456gpal8hk

Taproot was activated on Litecoin following Bitcoin's lead. It bundles three upgrades: Schnorr signatures (more efficient, enables signature aggregation), MAST (Merkelized Alternative Script Trees, which hides unused spending conditions), and a new script version that opens the door to future upgrades without hard forks.

For everyday single-signature transactions, ltc1p offers similar fees to ltc1q. The real benefits emerge with complex transactions: multisig setups, time-locked contracts, and atomic swaps. A 3-of-5 multisig transaction using Taproot can look identical to a simple single-sig transaction on the blockchain, which improves both privacy and efficiency. For advanced users running Lightning channels or atomic swaps between LTC and BTC, Taproot is the foundation of next-generation cross-chain infrastructure.

Wallet support for ltc1p is still catching up. Litecoin Core supports it fully. Some hardware wallets support receiving but not all signing modes. If you are a standard user sending and receiving LTC, ltc1q remains the practical choice. If you are involved in multisig, Lightning, or cross-chain swaps, ltc1p is worth using where supported.

MWEB stealth addresses: privacy by default

MWEB (MimbleWimble Extension Blocks) was activated on Litecoin in May 2022 and introduced a completely different address paradigm. MWEB stealth addresses do not follow the standard prefix conventions — they are significantly longer and encode the recipient's public scan key and public spend key. An MWEB address starts with ltcmweb1 and can be over 100 characters long.

When you send LTC to an MWEB address, the transaction amount is hidden. Observers on the blockchain cannot see how much was sent. The sender and receiver are cryptographically unlinkable. This is not mixing or tumbling — it is built into the protocol itself. No third-party service, no extra steps, no trust required.

To use MWEB, you need a wallet that supports it. Currently, Litecoin Core (v0.21.3+) and the Litewallet mobile app support MWEB. Hardware wallet support is limited. You can "peg in" to MWEB by sending from any standard address to your MWEB address, transact privately within the MWEB zone, and "peg out" back to a standard address when you need to interact with exchanges or services that do not support MWEB. Read the full deep dive in our MWEB guide.

Comparison table: all Litecoin address formats

FormatPrefixTechnologyFee levelError detectionPrivacyWallet support
Legacy (P2PKH)LOriginal (2011)HighestBasic checksumNoneUniversal
P2SH (SegWit wrapped)MSegWit 2017MediumBasic checksumNoneVery wide
Native SegWit (Bech32)ltc1qSegWit nativeLowestAdvanced (Bech32)NoneWide (recommended)
Taproot (Bech32m)ltc1pTaproot/SchnorrLowestAdvanced (Bech32m)Improved for multisigGrowing
MWEB stealthltcmweb1MimbleWimbleLow (MWEB fee)Built-inFull (amounts + parties hidden)Limited (Core, Litewallet)

Fee comparison: the numbers that actually matter

Transaction fees on Litecoin are low compared to Bitcoin and Ethereum, but relative differences between formats still add up. Here is what a typical 1-input, 2-output transaction costs at standard fee rates:

Address formatTypical TX size (vbytes)Fee at 1 lit/vBFee at 10 lit/vB (congested)Savings vs Legacy
L (Legacy)~226 vB0.00000226 LTC0.0000226 LTC
M (P2SH-SegWit)~167 vB0.00000167 LTC0.0000167 LTC~26%
ltc1q (Native SegWit)~141 vB0.00000141 LTC0.0000141 LTC~38%
ltc1p (Taproot)~139 vB0.00000139 LTC0.0000139 LTC~39%

During normal network conditions, the absolute difference is less than a penny. But during the Ordinals-driven congestion spike in mid-2023, Litecoin fees briefly jumped 50x above normal. Users on legacy addresses paid noticeably more. If you do DCA (dollar-cost averaging) with weekly buys and withdrawals, the savings compound over hundreds of transactions per year. Track current fee rates on our fee tracker and calculate exact costs with the LTC calculator.

War story — Sent LTC to a Bitcoin address and panicked: In 2018, a Reddit user reported sending 15 LTC to what they thought was a Litecoin address starting with "L." The problem: it was actually a Bitcoin legacy address starting with "1" — and the user had copy-pasted from the wrong tab. The L-prefix on Litecoin and the 1-prefix on Bitcoin use overlapping base58 address spaces, but the underlying keys are completely different. The LTC was broadcast to the Litecoin network but referenced an output that nobody controlled with Litecoin keys. The coins were effectively burned. Recovery was only possible because the user also controlled the corresponding Bitcoin private key (same HD wallet seed, different derivation path). By importing the Bitcoin private key into a Litecoin wallet, they were able to reconstruct the Litecoin spending key and recover the funds. This specific recovery path only works if you control the key on both chains. If you sent LTC to someone else's Bitcoin address, the coins are gone unless that person cooperates. This confusion is one reason Bech32 addresses (ltc1q) were designed — they are chain-specific and cannot be confused with Bitcoin's bc1q addresses.

How to check which format your wallet uses

Open your wallet and generate a new receive address. Look at the first characters:

  • Starts with L — you are on legacy. Time to upgrade.
  • Starts with M — you have SegWit, but the wrapped version. Good but not optimal.
  • Starts with ltc1q — you are on native SegWit. This is the recommended default.
  • Starts with ltc1p — you are on Taproot. You know what you are doing.
  • Starts with ltcmweb1 — you are using MWEB privacy addresses.

Some wallets let you choose the address type in settings. Ledger Live, for example, offers a choice between "Legacy" and "Native SegWit" when creating a Litecoin account. Always select Native SegWit. Electrum-LTC lets you choose at wallet creation time — select "Standard wallet" with "Native Segwit (p2wpkh)" for ltc1q addresses.

If your current wallet only supports L-addresses and the developer has not updated it, switch wallets. Our wallet ranking lists every wallet with its supported address formats.

Why you should switch to ltc1q now

If you are still using L or M addresses, here is the case for switching:

  1. Lower fees. 30-40% cheaper per transaction. Small in absolute terms, meaningful over time.
  2. Better error detection. Bech32 encoding catches typos that base58 misses. You will never send to a mistyped address.
  3. No ambiguous characters. Bech32 is lowercase-only and excludes 0/O/l/1 confusion. Try reading a legacy address over the phone versus an ltc1q address — the difference is night and day.
  4. Future compatibility. All protocol upgrades build on SegWit. Lightning Network requires SegWit. Atomic swaps require SegWit. If you want access to next-generation Litecoin features, you need SegWit addresses.
  5. Network health. SegWit transactions use block space more efficiently. By using ltc1q, you help the network process more transactions per block.

The migration is simple: create a new ltc1q wallet (or switch your existing wallet to native SegWit mode), send your LTC from your old address to your new address. Yes, you pay one transaction fee to migrate. That fee pays for itself after a handful of future transactions.

Sending between different address types

All Litecoin address formats are fully interoperable on the network level. You can send from an L-address to an ltc1q address, from an M-address to an MWEB address, from an ltc1p address to an L-address — any combination works. The Litecoin network does not care what format the sender or receiver uses. The fee you pay depends on your sending address format (and the number and type of inputs/outputs), not the receiving address format.

The only caveat is wallet and exchange support. Some older exchanges have not updated their withdrawal systems to support sending to ltc1q or ltc1p addresses. This is rare in 2026 but not zero. If an exchange rejects your ltc1q address, use an M-address as a fallback — every exchange supports M-addresses. Then move your funds from the M-address to your ltc1q wallet.

MWEB: when privacy matters more than convenience

MWEB is not just another address format — it is a fundamentally different transaction model. Standard Litecoin transactions are fully transparent: amounts, sender, receiver, all visible on the blockchain. MWEB transactions use confidential transactions (Pedersen commitments) to hide amounts and cut-through to remove the transaction graph. Nobody watching the blockchain can determine how much you sent or who you sent it to.

This matters for real use cases: paying salaries without revealing compensation, making business purchases without competitors seeing your supply chain, or simply exercising your right to financial privacy. MWEB is not about hiding illegal activity — it is about the same privacy you have when you pay cash at a store.

The trade-off: MWEB wallet support is limited, and some exchanges have delisted or restricted LTC specifically because of MWEB (South Korean exchanges were the first to do this). If you need to interact with services that do not support MWEB, peg out to a standard address first. Monitor MWEB adoption and peg-in/peg-out volume on our on-chain dashboard.

Frequently asked questions

Can I send LTC between different address types?

Yes. All Litecoin address formats are fully interoperable. You can send from any format to any other format. The fee depends on your sending address type, not the receiving type. L to ltc1q, M to ltc1p, ltc1q to MWEB — all work.

Which address format has the cheapest fees?

ltc1q (native SegWit / Bech32) and ltc1p (Taproot / Bech32m) offer the lowest fees. For standard single-signature transactions, ltc1q is the recommended default in 2026. The fee difference versus legacy L-addresses is roughly 30-40% per transaction. Check real-time fee rates on our fee tracker.

What is an MWEB address?

An MWEB address starts with ltcmweb1 and is used for privacy-preserving transactions on Litecoin's MimbleWimble Extension Block. When you send LTC to an MWEB address, the transaction amount is hidden and the sender-receiver link is broken. You need a wallet that supports MWEB (currently Litecoin Core or Litewallet). Read our MWEB deep dive for the full explanation.

My wallet gives me an L-address. Should I switch wallets?

Yes, unless your wallet allows you to change the address type in settings. If it only generates L-addresses and has no option for SegWit, the wallet is outdated. Switch to a wallet that supports ltc1q addresses — Litecoin Core, Electrum-LTC, Ledger, Trezor, Trust Wallet, and Exodus all do. See our wallet ranking for detailed comparisons.

I accidentally sent LTC to a Bitcoin address. Can I recover it?

It depends. If you control the private key on both chains (same seed, same derivation path), you may be able to import the Bitcoin private key into a Litecoin wallet and recover the funds. If you sent to someone else's Bitcoin address, recovery requires their cooperation — they would need to extract the private key and use it on the Litecoin network. If the address belongs to an exchange, contact their support, but success is not guaranteed. This confusion is why Bech32 (ltc1q) addresses are strongly recommended — they are chain-specific and cannot be confused with Bitcoin addresses.

Sources

  • BIP 173 — Bech32 address encoding specification (Pieter Wuille, Greg Maxwell)
  • BIP 350 — Bech32m address encoding for Taproot (Pieter Wuille)
  • LIP 2 — Litecoin SegWit address format specification
  • LIP 3 — MWEB (MimbleWimble Extension Blocks) specification
  • Litecoin Core documentation — address format and derivation path reference
  • Blockchair — transaction size and fee statistics across address formats
Jarosław Wasiński
Jarosław Wasiński
Editor-in-chief · Crypto, forex & macro market analyst

Independent analyst and practitioner with over 20 years of experience in the financial sector. Actively involved in forex and cryptocurrency markets since 2007, with a focus on fundamental analysis, OTC market structure, and disciplined capital risk management. Creator of MyBank.pl (est. 2004) and Litecoin.watch — platforms delivering reliable, data-driven financial content. Author of hundreds of in-depth market commentaries, structural analyses, and educational materials for crypto and forex traders.

20+ years in financial marketsActive forex & crypto trader since 2007Founder of MyBank.pl (2004) & Litecoin.watch (2014)Specialist in fundamental analysis & risk management

Track Litecoin in real time

Live rates for 30+ currencies, updated every second

Open dashboard