Cloud Dev Helpers
Choose a resource name, GCS address or service account JSON. Inspect one value at a time.
Processed in this browser’s memory. No input storage, upload, resource request or authentication.
Relative or full paired resource name. No API version or REST self link.
One value · 65,536 UTF-16 units · resource 4,096 · object 1,024 UTF-8 bytes · JSON depth 100.
Input or mode changed. Parse again before exporting.
A GCP resource name parser helps when a log gives you a long identifier but your configuration asks for its project or parent. Keep those parts separate from a storage URL and from a credential file: they describe different things. This workbench gives each input type an explicit mode and an inspectable JSON report.
The GCP resource name parser keeps collection names paired with their IDs. A full name adds the service host; a relative name leaves that field empty. Parent and leaf are shown separately, and a numeric project token stays a number-shaped string rather than being guessed into a project ID.
The service account view builds its report from a fixed field allowlist. It replaces private_key with a redaction marker and counts unknown fields without repeating their names or values. The original text remains in the input; inspect visible project and account metadata before sharing a report.
Switching modes keeps your text and invalidates its old result. Resource names, GCS addresses and service account JSON have separate rules. Use Example to preview a fictional input for the currently selected mode before replacing your own text.
For gs to https conversion, the object part of gs:// is literal: %20 stays three characters and becomes %2520 in HTTPS. An HTTPS path is decoded exactly once. A plus sign remains a plus, and repeated slashes remain part of the object name.
Automatic parsing waits 350 ms after editing. Turn it off for the Parse button or Ctrl/Cmd + Enter. Edits immediately disable exports. Example and Clear require a preview; Undo restores the input and its previous result, including a stale result.
Inspect Google Cloud resource names in relative form or with a //service.googleapis.com prefix. The report lists collection/ID pairs, parent, leaf and recognizable project, organization, folder and location scopes. It distinguishes a numeric project token from an ID without claiming that they identify the same project.
Convert between gs:// and the standard storage.googleapis.com path endpoint. A DNS-compatible bucket also gets a virtual-hosted URL. Bucket, object and UTF-8 byte length remain visible. Dotted or underscore-containing bucket names use the path endpoint; no alternate host is guessed.
The service account JSON viewer requires the service_account type and essential string fields. It rejects duplicate JSON keys, unsafe numeric values and invalid HTTPS metadata URLs. PEM inspection checks the text envelope and base64 shape only. Optional known metadata is retained; unknown fields are counted.
A full name starts with a service host, followed by the relative resource path. The report separates that hierarchy so you can identify the service and parent. Actually finding the resource in a project requires the relevant console or API and suitable permissions; this page cannot establish that it exists.
In Cloud Storage, identify the bucket and the exact object name. Their gs form is gs://bucket/object. Select GCS mode to convert a supported HTTPS object address or inspect an existing gs value. A bucket alone is accepted too, but its URL does not refer to a particular object.
For the supported XML API form, the path URL is https://storage.googleapis.com/bucket/object with the object correctly encoded. This tool generates that HTTPS spelling. It does not make a private object public, add a signature or remove the need for authorization; an access error is not an encoding diagnosis.
An ID and a project number are distinct identifiers. The parser can recognize an all-digit project token, but it cannot derive the corresponding ID or number from text alone. Use an authorized Google Cloud project lookup when you need that mapping, and preserve whichever identifier the target API requires.
Do not commit an actual private service account key to a repository. This viewer’s JSON export has the private key redacted, but visible metadata still needs review before sharing. If a real key has already been exposed, removing one copy is insufficient; follow Google Cloud’s key replacement and deletion procedure.
Is a supported input behaving unexpectedly?
Use the GCP resource name parser to read a hierarchy, then select GCS or service account mode when the input belongs to a different format.