SegWit compatibility on old sites and other wallets?

[DragonLancer]

Hello, as Electrum 3.0 came out I downloaded it and created SegWit wallet. I did this because I heard that SegWit makes fees very low and transactions will go faster. And now I've got confused - addresses look totally different, like this: bc1qy4veh20************6n4xt99swt7qvjr, like all of these look this way.
They are longer and start with bc. Why is it like this? If I will paste address like this in site and the site won't recognize this address as Bitcoin address? Am I supposed to create old version wallet then? I'm confused, excuse me if there are any grammar errors.

[1714986010]

1714986010

[1714986010]

1714986010

[1714986010]

1714986010

[TryNinja]

Since someone already answered this question, I'm just going to quote a post by @PVminer here (100% credits to him):

I just created a new segwit wallet but my new address start with bc1*************** and not with 3*********
Why?

This is a native segwit standard (so called bech32 address using P2WPKH) but this is not yet supported by merchants or other wallets. The addresses starting with 3 are P2SH addresses. They can specify many things, including segwit embedded inside P2SH (P2SH-P2WPKH). I figured out how to create such a wallet in Electrum (use BIP39 seed and m/49'/1'/0' derivation path) but it may be better to wait for some more official tutorials.

Unfortunately, segwit wallets are not standardized yet and there might be problems with importing/exporting keys between wallets.

The address is valid but not yet supported by many Blockchain explorers and services with an address validator (e.g: Blockchain.info, Blockcypher...)

[DragonLancer]

Thank you very much for this! So, as I thought, I need to wait for sites and payment providers to accept SegWit standard. IMO they should do it when SegWit was released to public network...