An ampersand often separates query parameters in a playlist URL. In HTML source it may be written as &, but the address pasted into a player normally needs the actual ampersand character. Copying an escaped HTML representation literally can change parameter names and stop the service from recognizing the request.
Know whether you copied an address or source code
A browser’s copy-link command usually gives the actual URL. Copying from HTML markup or a code sample may give escaped text instead. Use the original service instructions and preserve the full sequence of query parameters.
Do not simplify account parameters
Removing everything after the first ampersand can remove a required password, format or output setting. The values should be handled as a complete URL. If a link appears malformed, request a fresh copy rather than inventing parameter names.
Keep examples synthetic
A query string can expose credentials even when the hostname looks harmless. For public troubleshooting, replace all private values and use example.invalid. The shape of the URL is enough to explain an escaping problem.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A literal query ending ?user=demo&type=list may be interpreted differently from ?user=demo&type=list. Neither example here is a working service URL.
Questions about this topic
Can I remove the part after an ampersand?
Not safely without knowing the service’s URL requirements.
Is ampersand escaping an account problem?
It is a text-copying problem that can prevent the account request from being understood.
