Blink Component Embed

Turn a section's saved JSON settings and a default-value render statement into a ready-to-paste render statement with the real values baked in — no manual copy-pasting field by field.

Open tool โ†’
๐Ÿงฉ

Section JSON in

Paste the JSON for a section or block — including its settings object — straight from a template JSON file.

๐Ÿงพ

Render statement in

Paste the {% render %} statement whose keys reference those settings with default placeholder values, e.g. ss.show_homepage.

โšก

One click to populate

Every value reference is matched to the matching key in the JSON's settings and swapped in as a real Liquid literal.

๐Ÿ“‹

Copy and go

The populated render statement keeps your original formatting and line breaks — copy it straight into a template.

1

Paste the section JSON

Copy the section or block's JSON — from a template file, theme export, or the Shopify editor — and paste it into the first box. It doesn't need to be wrapped in outer braces; a bare "id": { "settings": {...} } fragment works fine.

2

Paste the render statement

Paste the {%- render 'snippet', key: ss.setting_id -%} statement into the second box. Each value should reference a setting, e.g. ss.show_homepage — the last part after the dot is matched against the JSON's settings keys.

3

Click Populate

The third box fills with a new version of the render statement, with each ss.xxx reference replaced by the real value from the JSON — strings quoted, numbers and booleans left bare.

4

Check the summary, then copy

A summary below the boxes shows how many values were populated and flags any keys it couldn't find a match for — those are left untouched rather than guessed at. Use Copy to grab the result.

A render statement like this:

{%- render 'blink-schema-snippet',
  visible_homepage: ss.show_homepage,
  organisation:      ss.organization
-%}

combined with section JSON containing:

"settings": {
  "show_homepage": true,
  "organization": "BlinkSEO"
}

becomes:

{%- render 'blink-schema-snippet',
  visible_homepage: true,
  organisation:      'BlinkSEO'
-%}
Nothing is fabricated. If a render key's setting can't be found in the pasted JSON, that line is left exactly as it was (still referencing ss.xxx) and called out in the warnings list — it's never replaced with a guess.
Values with filters (e.g. ss.telephone | strip_html) still get the variable part replaced, with the filter chain preserved after it. Values that aren't a simple settings reference at all (already a literal, or something more complex) are left untouched.