Link-value 1
next- Raw target
- /articles?page=2
- Resolved target
- https://example.com/articles?page=2
- rel
- next
- title
- Next page
Web linking metadata
HTTP Link Header Parser & Inspector
Split multiple link-values correctly, preserve commas and semicolons inside quoted parameters, inspect relation types, and resolve relative targets against a context URL.
Input is processed locally in this browser
HTTP Link header parser workspace
Relative target references are resolved against this URL for inspection only.
Link-values
2
Relations
2
Problems
0
Link-value 2
preload- Raw target
- /styles/app.css
- Resolved target
- https://example.com/styles/app.css
- rel
- preload
- as
- style
Normalized field value
</articles?page=2>; rel="next"; title="Next page", </styles/app.css>; rel="preload"; as=styleSee every typed link in one response field
The HTTP Link field connects a context resource to one or more target resources. It powers uses such as pagination, preloading, alternate representations, and canonical hints. Each target sits inside angle brackets and is followed by parameters; a single field can carry several link-values.
How to use the HTTP Link header parser
- Paste the field value from an HTTP response. Including the
Link:field name is optional. - Enter the response or context URL when the field contains relative target references.
- Review every target, resolved target, relation type, and extension parameter separately.
- Correct malformed or duplicate parameters, then copy the normalized field value for comparison or tests.
Pagination example
</articles?page=2>; rel="next"The context is the current response; the target is the next page. The relation type explains the link instead of relying on URL shape.
Preload example
</styles/app.css>; rel=preload; as=styleA syntactically valid preload is not automatically beneficial. The resource type, credentials mode, priority, cacheability, and actual page use must agree.
Standards, resolution, and limits
Parsing follows the Web Linking model and field serialization in RFC 8288. Registered relation names are maintained separately by IANA. This tool reports relation tokens but does not claim that a token is registered or that a recipient implements it.
The optional context URL resolves relative references for inspection with the browser's URL implementation. No target is fetched. Normalization preserves the first occurrence of a parameter and warns about duplicates; production code should decide whether an invalid field is ignored, rejected, or logged at its trust boundary.
Frequently asked questions
Why can a Link header not be split on every comma?
A field can contain several comma-separated link-values, but a quoted parameter such as title="Chapter one, continued" can also contain a comma. A correct parser tracks quoted strings and URI angle brackets before splitting.
What does the rel parameter describe?
rel names the relationship between the context resource and the target resource. It can contain one or more registered relation types such as next, prev, canonical, preload, or an extension relation URI.
How are relative Link targets resolved?
A relative target is resolved against the context IRI of the Link field. Enter that response or resource URL in the optional context field to see an absolute inspection value; the raw target is preserved.
Does Toolk request any target URL from the header?
No. The parser only reads the text you paste and uses the browser URL constructor for optional resolution. It does not fetch, validate, preload, or contact any target.
Related developer tools
Last updated: August 29, 2026
Need a different tool?
Browse all 99 browser-based tools (99 currently marked free), or tell us what useful utility we should build next.