ProductPassKitBrowse tools
Menu

GS1 Digital Link

GS1 Digital Link Decoder

Inspect the GS1 Application Identifiers and URI structure carried by a Digital Link.

The URI is parsed locally. ProductPassKit does not request or probe the URL.

Ready

The URI stem, identifier, qualifiers, attributes and extensions will appear here.

Private by design: Your input is processed locally in your browser and is not uploaded to ProductPassKit.

Understand the parts of a Digital Link

A decoded URI is divided into the stem, the primary GS1 identification key, qualifying identifiers, data attributes and any non-GS1 extension parameters. This makes it easier to see which data identifies the item and which data describes it.

Example structure

/01/09520123456788/10/ABC123?17=270101AI (01) is primary, AI (10) qualifies the item by batch, and AI (17) is an attribute.

Safe interpretation

AI names come from the Syntax Engine’s embedded GS1 data. Dates are shown in a neutral YY-MM-DD representation so the decoder does not invent a century or business meaning not present in the source.

Local JSON output

The JSON copy action is generated entirely in the browser. ProductPassKit does not create a share URL, store an identifier history or send the URI to analytics.

Frequently asked questions

Are arbitrary query parameters treated as GS1 data?

No. Non-AI parameters are separated as extension parameters rather than assigned invented GS1 meaning.

Can I export the decoded values?

Yes. The parsed result can be copied as locally generated JSON.