Git URL Converter
Convert Git repository URLs instantly between SSH, HTTPS, and Web formats with organization and repository parsing.
Do it offline:$
How to use it
- Paste your existing Git URL into the input field above. The tool automatically detects whether it is an SSH, HTTPS, or web address.
- Inspect the parsed repository metadata including the host, organization/user, repository name, and protocol.
- Click the Copy button next to any desired target format — SSH clone syntax, HTTPS URL, Web browser link, or full git clone command.
Convert any Git repository URL between SCP-style SSH, standard RFC SSH, HTTPS, and browser web URLs instantly in your browser. Parse owner, organization, and repository names with zero network requests.
How it works
Git uses multiple conventions for remote repository addressing. SCP-like syntax (git@host:owner/repo.git) relies on OpenSSH default port 22 and relative path resolution.
Standard URL syntax (ssh://git@host:port/owner/repo.git) allows explicit non-standard ports commonly required in corporate or self-hosted Git instances.
HTTPS addresses enable token-based authentication and firewall traversal, while web URLs strip the .git suffix for browser inspection.
All conversions run client-side using deterministic URL parsing algorithms without sending your internal repository addresses across the wire.
Examples
Every example on this page is executed against the same engine that powers the tool, on every build.
Gotchas worth knowing
Common errors
FAQ
Why does git clone fail with 'Permission denied (publickey)'?
This error occurs when using an SSH URL without a registered SSH key in your GitHub or GitLab account. Switching to the HTTPS URL format or adding your public key (ssh-add) resolves the issue.
What is the difference between git@github.com:owner/repo.git and ssh://git@github.com/owner/repo.git?
The first is SCP-style syntax, which assumes port 22. The second is an RFC-compliant URI format that supports custom port numbers (e.g., ssh://git@host:2222/owner/repo.git).
Does this tool send my private repository URLs to a server?
No. All parsing and URL transformations happen entirely inside your browser's JavaScript engine. Your URLs and internal repository paths never touch any server.