Quick answer
An M3U route supplies a playlist or playlist URL. A server-login route asks for an address and credentials separately. Use the account format confirmed for the installed player.
Read the visible fields
A local playlist name is usually a label you choose, while a server address points to the issued service. A username and password belong in their matching fields. A player that accepts a private playlist URL may request a different form. Similar app branding does not make those forms interchangeable.
Treat the complete URL as private
A playlist address can contain account credentials or access tokens in its path or query. Hiding only the password box is insufficient when the full URL remains visible elsewhere. Keep the address out of public screenshots, browser searches, comments and unverified conversion services.
Do not guess the conversion
Changing a URL suffix or rearranging parameters is not a verified way to obtain another supported account route. Ask whether the issued account can use the format your player needs. A public format description does not establish the correct private endpoint, entitlement or current service details.
Compare one profile at a time
Preserve a working profile before creating a supported alternative. Give local labels distinct names, close the earlier stream and test one reference source. If live TV loads but a library section does not, report that narrower scope rather than repeatedly importing unrelated lists.
Know what the comparison proves
A profile opening demonstrates that particular input and account state on the tested route. It does not prove every feature, EPG source, archive function or player build is supported. Record the exact app/version and the action that succeeds or fails for follow-up.

























