Cloud Storage URI Parser

How to use

1. 1Keep Parse a URI selected and paste an s3://, gs://, or az:// URI, or an HTTPS storage URL such as a bucket.s3.region.amazonaws.com, storage.googleapis.com, or account.blob.core.windows.net link.
2. 2Read the detected provider, the input form, and for S3 whether it is virtual-hosted or path-style.
3. 3Review the breakdown: bucket or container, object key or blob path, region, storage account, file name, and extension.
4. 4Copy the native URI or the HTTPS endpoint from the output rows to convert between the two forms.
5. 5Check the notes for bucket-naming problems, a missing region, or a dropped SAS token.
6. 6Switch to Build a URI to assemble one from scratch: pick a provider, fill the fields, and copy the generated URI and endpoint. Use the sample buttons to see each format.

About this tool

Cloud Storage URI Parser decodes the object-storage addressing schemes of the three dominant cloud providers, all in your browser. Object storage looks simple until you have to read a raw URL out of a log line, a Terraform plan, an SDK error, or a teammate's message and work out exactly which bucket, key, region, and account it points to. This tool removes that guesswork. It understands two kinds of input for each provider: the native URI scheme and the public HTTPS endpoint. For Amazon S3 it parses s3://bucket/key URIs and every common HTTPS form: virtual-hosted style (bucket.s3.region.amazonaws.com and the legacy global bucket.s3.amazonaws.com) and path-style (s3.region.amazonaws.com/bucket/key and the global s3.amazonaws.com/bucket/key). It tells you which style was used, which matters because virtual-hosted is the modern default and path-style is being retired for new buckets, and it pulls out the region embedded in the host when one is present. For Google Cloud Storage it parses gs://bucket/object URIs and the storage.googleapis.com and storage.cloud.google.com HTTPS endpoints, including the virtual-hosted bucket.storage.googleapis.com form. For Azure Blob Storage it parses az:// (and azure://) URIs and the account.blob.core.windows.net HTTPS endpoint, splitting out the storage account, the container, and the blob path, and quietly dropping any SAS query string so you see the clean object location. Whatever you paste, the parser shows the logical pieces (bucket or container, object key or blob path, region, account, file name, and extension) and then gives you both canonical forms back: the native URI and the public HTTPS endpoint, each with its own copy button. That bidirectional conversion is the part people search for most: turning an s3:// URI into a clickable https link, or reducing a long virtual-hosted URL back to the short s3:// form a CLI command wants. Object keys are percent-decoded on the way in and re-encoded per segment on the way out, so spaces and unicode in file names round-trip correctly while the slashes that define the key prefix are preserved. The tool also flags the bucket-naming mistakes that bite people: uppercase letters, underscores, names that are too short or too long, names shaped like IP addresses, and bad leading or trailing characters, plus a reminder that a regionless S3 endpoint resolves to us-east-1. A Build mode flips the workflow: choose a provider, type the bucket or container, optional key, region, or account, and the tool assembles a correct native URI and HTTPS endpoint for you. Switching modes preserves the values, so you can paste a URL, load it into the builder, change the region or the key, and copy the result. Useful for writing IAM and bucket policies, debugging access errors, building presigned-style base URLs, normalizing storage references for inventory exports, and learning how the three providers differ. Everything runs locally with plain string and URL handling; no bucket name, account, or object key you paste is uploaded.

Free to use. Works in your browser. No signup, no login.