What are rendering parameters in Sitecore?

Rendering parameters are key/value settings attached to a rendering on a page — things like CSS class, column count, or display variant. They configure how a component renders without changing its data source content. They are stored URL-encoded in the rendering's Parameters field.

How are rendering parameters stored?

As a URL-encoded query string (key1=value1&key2=value2) in the s:par attribute of the rendering's element inside the page item's __Renderings (Layout) or __Final Renderings field. Inside the XML, the ampersands are escaped as &.

What do the attributes on the element mean?

uid is the unique instance ID of the rendering on the page; s:id is the rendering definition item's ID; s:ph is the placeholder key the rendering is bound to; s:ds is the data source item path or ID; s:par holds the URL-encoded rendering parameters.

When should I use rendering parameters vs. data source fields?

Use data source fields for content (text, images, links) that editors author. Use rendering parameters for presentation settings (styling, layout variants) — Helix guidance notes parameters are less editor-friendly and often restricted to more technical users.

Does this work with SXA and headless (JSS) implementations?

The underlying storage format is the same. SXA adds its own base parameters (like Styles and GridParameters) and headless implementations surface params through the Layout Service JSON — but the s:par query-string encoding generated here is what gets stored either way.

Wasim's Site

Sitecore Rendering Parameters Generator

Generate Sitecore rendering parameters and layout XML — the URL-encoded Parameters string plus the <r /> rendering element with s:par, s:ph, and s:ds.

Rendering

Rendering Item ID (GUID)

Rendering UID

Placeholder

Data Source (optional)

Parameters

Name

Value

CssClass = hero-banner

Parameters String (Parameters field value)

URL-encoded key/value pairs — the raw value stored in the rendering's Parameters field.

CssClass=hero-banner

Rendering Element (<r />)

The single rendering definition with s:par — paste into an existing layout/final layout field.

<r uid="{DB9056E6-A939-494F-8DCE-ECB662496428}" s:id="{RENDERING-ITEM-ID}" s:ph="main" s:par="CssClass=hero-banner" />

Full Layout XML (default device)

A complete presentation XML wrapper containing the rendering under the Default device.

<r xmlns:p="p" xmlns:s="s" p:p="1">
  <d id="{FE5D7FDF-89C0-4D99-9AA3-B5FBD009C9F3}">
    <r uid="{DB9056E6-A939-494F-8DCE-ECB662496428}" s:id="{RENDERING-ITEM-ID}" s:ph="main" s:par="CssClass=hero-banner" />
  </d>
</r>

Sitecore Rendering Parameters, Without Hand-Encoding

Every Sitecore developer has squinted at a __Renderings field trying to hand-edit an URL-encoded parameters string inside XML-escaped attributes. One wrong & or an unencoded space and the presentation breaks. This generator builds the three artifacts you actually need — the raw parameters string, the single rendering <r /> element, and a full default-device layout wrapper — with all encoding handled for you.

The Encoding Layers

Layer 1 — URL encoding: parameter keys and values are query-string encoded (CssClass=hero%20dark).
Layer 2 — XML escaping: when stored in the s:par attribute, ampersands become &.
GUIDs: the rendering uid must be unique per page; the tool generates valid braced, uppercase GUIDs.

How to Use This Generator

Enter the rendering item ID (from the rendering definition under /sitecore/layout/Renderings).
Set the placeholder and data source as needed; generate a fresh UID.
Add parameters one key/value at a time.
Copy the output that fits your task — the params string for a Parameters field, or the XML for layout deltas, serialization files, and code reviews.

Frequently Asked Questions

What are rendering parameters in Sitecore?: Rendering parameters are key/value settings attached to a rendering on a page — things like CSS class, column count, or display variant. They configure how a component renders without changing its data source content. They are stored URL-encoded in the rendering's Parameters field.
How are rendering parameters stored?: As a URL-encoded query string (key1=value1&key2=value2) in the s:par attribute of the rendering's <r /> element inside the page item's __Renderings (Layout) or __Final Renderings field. Inside the XML, the ampersands are escaped as &.
What do the attributes on the <r /> element mean?: uid is the unique instance ID of the rendering on the page; s:id is the rendering definition item's ID; s:ph is the placeholder key the rendering is bound to; s:ds is the data source item path or ID; s:par holds the URL-encoded rendering parameters.
When should I use rendering parameters vs. data source fields?: Use data source fields for content (text, images, links) that editors author. Use rendering parameters for presentation settings (styling, layout variants) — Helix guidance notes parameters are less editor-friendly and often restricted to more technical users.
Does this work with SXA and headless (JSS) implementations?: The underlying storage format is the same. SXA adds its own base parameters (like Styles and GridParameters) and headless implementations surface params through the Layout Service JSON — but the s:par query-string encoding generated here is what gets stored either way.

Official Resources

Sitecore Helix Documentation — including rendering parameters guidance (GitHub)