Short answer: paste the command exactly as you ran it, pick fetch or raw HTTP. Anything the converter did not understand is named under the result rather than dropped.
What maps to what
-X→method; a body without-Xbecomes POST.-H→headers, one entry per flag, value untouched.-d,--data-raw,--data-binary→body.-u→ anAuthorization: Basicheader.-G→ the data moves into the query string.-F→ reported, not generated: a browser cannot attach a file by path.
What a converter cannot fix
A working terminal request is not automatically a working browser request. CORS, cookies and client certificates behave differently in a page. When the snippet fails with a blocked request, the server’s policy is the problem, not the conversion.
Comparing two versions of the same command? The text diff shows exactly what changed.