LOKAL Open the generator
LOKAL / Advertising rules / Utah

Utah Division of Real EstateUtah Admin. Code R162-2f-401hRead at the source

Real estate advertising rules in Utah

A licensee may not advertise real estate services or property in any medium without clearly and conspicuously identifying the brokerage they are affiliated with, using the brokerage name as shown on Division records.

What has to be on the post

The part that is easy to get wrong

Utah excuses the brokerage name only when a licensee advertises their OWN property and signs the ad as owner-agent or owner-broker.

The numbers, in one place

Utah advertising requirements, in figures
1requirement Utah Division of Real Estate puts on the ad itself
51US jurisdictions LOKAL carries, read at the source
15of them set a text SIZE rule, not just a mention
2require the licence number on the advertisement
no ratioUtah fixes no size ratio between the two
2026the year this rule was last read at the source
29 %of US jurisdictions turn this into a measurable size rule
14,853US markets LOKAL can pre-fill, down to the ZIP code
$29a month for the tool that checks this before you post

A worked example, and why one template cannot do it

Two states contradict each other outright, and it is the clearest case study of why this matters. Texas asks for the broker name at 50 % of the largest agent contact text; Illinois asks for 100 %. A layout built for Texas is therefore non-compliant in Illinois, and the difference is not a missing word but a font size. That result is only visible if something measures the pixels after drawing them, which is what LOKAL does before you post.

Where this comes from

Utah Division of Real Estate, Utah Admin. Code R162-2f-401h. Read the rule at the source

Your state regulator is not the only one with a say. These federal sources apply on top of Utah Admin. Code R162-2f-401h, and no state commission will remind you of them:

LOKAL reproduces published regulator guidance and checks what it draws against it. It is not legal advice, and it does not replace your broker's review.

LOKAL checks this on the image, not on a form.

Pick your market, set your signature once, and LOKAL measures what it actually drew against Utah Admin. Code R162-2f-401h before you post. It carries all 51 US jurisdictions.

Open the generator for Utah

Other jurisdictions

TexasVermontVirginiaDelawareIllinoisAll 51 jurisdictions

Questions

What must appear on a real estate ad in Utah?
Under Utah Admin. Code R162-2f-401h, Utah Division of Real Estate requires the licensed name of your brokerage. A licensee may not advertise real estate services or property in any medium without clearly and conspicuously identifying the brokerage they are affiliated with, using the brokerage name as shown on Division records.
Does a social media post count as advertising in Utah?
Utah Division of Real Estate writes its rule for advertising in any medium, and a market-update post that invites contact is advertising. The safest place for the disclosures is inside the image itself, because a caption can be truncated and a bio can be missed.
Is there a size requirement in Utah?
Utah sets no size or prominence ratio between the brokerage name and your own. The mention has to be there and be readable; how big it is relative to your name is not fixed by Utah Admin. Code R162-2f-401h.
Anything easy to get wrong in Utah?
Utah excuses the brokerage name only when a licensee advertises their OWN property and signs the ad as owner-agent or owner-broker.

How this page is written and checked

Written by the engineering team at INEYA Studio, the software studio that builds LOKAL. The Utah rule on this page was read at Utah Division of Real Estate's own published text in 2026, not summarised from a third party.

It is checked automatically on every build against the compliance table the product itself applies: Utah Admin. Code R162-2f-401h appears on this page only because LOKAL enforces exactly that rule when it draws your image. A page that claimed a requirement the product does not check would fail the build.

Reviewed by the engineering team at INEYA Studio on 2026-09-17, and re-checked automatically on every deployment. Found something out of date? Tell us and we will correct it.