When are custom thresholds worth it for Images render at the right size?
When are custom thresholds warranted?
Override `maxUpscalePercent` when your quality bar is genuinely different. Tighten it toward 100 when your brand is design-led and every asset is expected to be exported at its display size, which turns the check into an asset-pipeline gate. Loosen it when you knowingly reuse a library of fixed-size assets across layouts of varying widths, and your goal is to catch gross mistakes rather than every soft edge.
When should you stay on Standard?
Stay on 125 when you have no explicit asset-export standard, because it is the value that separates visible blur from harmless imprecision. Keep it when several teams or agencies contribute templates and you want one comparable bar. If your real complaint is that images look bad on retina screens generally, tightening this threshold only addresses part of it — the export practice is the fix, and the threshold merely reports on it.
What do you trade away?
Tightening toward 100 produces many findings on any template that reuses assets, and unless someone owns re-exporting them the check becomes a list nobody works through. Loosening it lets genuinely soft images pass, and because blur is gradual there is no point at which the failure announces itself — you simply stop hearing about it. Either change breaks comparison with earlier runs, so a template that looks improved may only be measured differently.
Community Standard vs org Custom
The Standard value is a general visual-quality judgement rather than a vendor rule, chosen so a pass means something without configuration. A Custom value expresses your own asset-production standard and belongs wherever that standard lives, with the reasoning recorded so it is not quietly relaxed after one awkward campaign. If you tighten it, pair the change with an owner for asset re-export, because a threshold nobody acts on is noise.
Worked override examples
A design-led brand sets `maxUpscalePercent` to `100`, requiring every asset to be exported at or above its display size and turning the check into a pipeline gate. A retailer reusing a fixed product-image library across several layout widths sets it to `150`, accepting mild softness to keep the findings limited to genuine mistakes. A team auditing an agency's template keeps `125`, because the value of the default there is that it is not a number either side chose.
How does an agent call it with parameters?
{
"type": "email",
"validations": [
{
"id": "email-image-rendering",
"parameters": {
"maxUpscalePercent": 125
}
}
]
}