Convert a git remote between HTTPS, SSH and the scp-like form, and see it taken apart — the scp form is not a URL and must not be parsed as one.
Waiting for a remote URL
One per line. HTTPS, SSH, the scp-like form and git:// are all read.
The conversion appears here
Paste one or more remote URLs in any form.
git@github.com:owner/repo.git is not a URL. It is scp syntax, where the colon separates the host from the path rather than introducing a port — which is why handing it to a URL parser gives you a port of “owner”. The real SSH URL has a slash: ssh://git@github.com/owner/repo.git. Both work with git; only one works with anything else.
Git Remote URL Converter runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
`git@github.com:owner/repo.git` looks like a URL and is not one. It is scp syntax, where the colon separates the host from the path rather than introducing a port — which is why handing it to a URL parser gives you a host of `github.com` and a port of `owner`, and why so much tooling mangles it. The real SSH URL has a slash: `ssh://git@github.com/owner/repo.git`.
That distinction is the reason this tool exists rather than being a find-and-replace. It parses all four forms properly and converts between them, including the GitLab subgroup case where the owner contains slashes and most converters give up.
Which form you want is a real decision with real trade-offs. HTTPS works everywhere, including behind a corporate proxy, and needs a credential helper or a token that eventually expires. SSH needs a key on the machine and is unaffected by token expiry, and is blocked by some networks. Neither is better, and the page says what each costs rather than recommending one.
Once a remote is parsed, the links a repository implies come with it — issues, pull requests, branches — built from each host's real URL layout rather than one guessed shape. A GitLab merge request lives at `-/merge_requests` and a Bitbucket pull request at `pull-requests`; assuming GitHub's layout produces links that 404.
No, and that is the point. It is scp syntax: the colon separates host from path, it does not introduce a port. A URL parser reads `owner` as the port number. The equivalent real URL is ssh://git@github.com/owner/repo.git, with a slash.
HTTPS works through proxies and firewalls that block SSH, and needs a token or credential helper that will expire. SSH needs a key on each machine and never expires. For a laptop you control, SSH is usually less friction; on a managed or shared machine, HTTPS often is.
When the server listens on a non-standard port. The scp-like form has nowhere to put a port — the colon is already doing the host-path job — so `ssh://git@host:2222/owner/repo.git` is the only way to express it.
No. It is conventional and most hosts accept the URL with or without it. The switch is there because some tooling compares remote strings literally and a mismatched suffix then looks like a different remote.
`git remote set-url origin <url>`. It only changes your local configuration — nothing is pushed and nothing about the repository changes.