> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/api-and-platform/widgets/privacy-widgets/edit-a-widget/content-and-design/breakpoints.md).

# Breakpoints

Breakpoints allow you to define responsive widget styles that adapt to different screen sizes, ensuring optimal rendering on mobile, tablet, and desktop.

### **Breakpoint Definitions**

<table><thead><tr><th width="100">Key</th><th>Width (px)</th><th>Device Type</th></tr></thead><tbody><tr><td><code>sm</code></td><td><code>576</code></td><td>Mobile</td></tr><tr><td><code>md</code></td><td><code>768</code></td><td>Tablet</td></tr><tr><td><code>lg</code></td><td><code>992</code></td><td>Laptop</td></tr><tr><td><code>xl</code></td><td><code>1200</code></td><td>Desktop/Large screen</td></tr></tbody></table>

{% hint style="info" %}
Breakpoint values are predefined and cannot be customized.
{% endhint %}

### How Breakpoints Work

* The default object defines base styles applied across all screen sizes.
* Each breakpoint (sm, md, lg, xl) can override specific style properties as needed.
* Breakpoints follow a mobile-first approach: smaller screens inherit from default unless explicitly overridden.

#### Example: Responsive DidomiStyle Payload

```json
"style": {
  "default": {
    "backgroundColor": "#ffffff",
    "padding": "12px",
    "borderRadius": "4px",
    "borderWidth": "1px",
    "boxShadow": "0px 2px 6px rgba(0,0,0,0.1)",
    "margin": "8px 0",
    "color": "#000000",
    "fontSize": "14px",
    "lineHeight": "1.5",
    "fontWeight": "400"
  },
  "sm": {
    "fontSize": "14px"
  },
  "md": {
    "fontSize": "16px"
  },
  "lg": {
    "fontSize": "18px"
  },
  "xl": {
    "fontSize": "20px"
  }
}
```

In this example:

* The widget starts with a default layout
* `fontSize` increases progressively at each screen breakpoint

{% hint style="info" %}
See [DidomiStyle](/api-and-platform/widgets/privacy-widgets/edit-a-widget/content-and-design/options.md#didomistyle) Options for additional breakpoint examples using the API.
{% endhint %}

***

### Best Practices

* Always define a default style as fallback
* Only override what’s necessary at each breakpoint
* Test styles on real devices or using responsive preview tools


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.didomi.io/api-and-platform/widgets/privacy-widgets/edit-a-widget/content-and-design/breakpoints.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.