The MLS Field That Stayed Behind, and the Disclosure Risk It Created

An MLS disclosure field does not travel with a listing photo when that photo is downloaded, shared, cropped, or posted to social media. A burned-in, state-specific disclosure label and a public provenance page keep the altered-image context attached to the asset beyond the MLS.

In April 1970, Apollo 13 had a problem that became urgent because one part could not fit the place where it was needed. The command module carried square lithium hydroxide canisters. The lunar module had round receptacles. After the mission’s oxygen-tank failure, the crew relied on the lunar module, and carbon dioxide management became a live concern. NASA’s Apollo 13 Flight Journal documents the workaround that let the crew use the square canisters in the round system.

The equipment existed. The information and materials existed. But they were separated by an interface that did not carry them forward.

That is a smaller-stakes version of what can happen on upload night. Your MLS may have a field for altered-image disclosure. ARMLS, for example, requires disclosure of digitally altered images in the MLS. Then a staged living-room image leaves the listing record: an assistant downloads it for Instagram, a seller shares it in a neighborhood group, or the image is cropped for a vertical post. The field stays behind.

The MLS record and the image take different routes

An MLS disclosure can be appropriate and complete within the MLS. It is still metadata in a specific system. Social platforms, email attachments, text messages, listing presentations, and downloaded JPEGs do not reliably bring that field along.

That creates a practical review problem. An agent may have disclosed the virtual staging properly in MLS remarks or a platform-specific disclosure field, while the same image appears elsewhere with no visible context. A buyer, seller, or cooperating agent sees furnishings that were added digitally, but has no way to tell that the image was altered.

The risk is less about assuming every platform handles disclosures badly and more about recognizing that each distribution path behaves differently. An image is portable. A field attached to one listing system often is not.

For a closer look at how disclosure can disappear during image handling, see What Happens When a Virtual Staging Disclosure Is Missing at Upload?.

A burned-in label travels with the photo

A burned-in label places the disclosure in the image itself. When the photo is exported, resized, attached to an email, or posted outside the MLS, the context remains visible unless someone removes it through a crop or edit.

That does not make every placement correct by default. Labels still need review for legibility, state-specific wording, and the way an image is framed on each channel. A label placed too close to an edge can disappear in a social crop. A tiny disclosure can technically remain in the file while becoming useless to the person looking at it.

The useful operating standard is straightforward: review the actual exported asset, not only the source image. Check the square listing image, the vertical social version, and any video thumbnail or slideshow frame that uses the staged photo.

NestPath Listing Studio creates virtually staged images with a burned-in, per-state AI-disclosure. That gives the agent a version designed to retain disclosure context outside the MLS, while leaving the agent responsible for confirming the wording and placement meet their state association’s guidance and their own legal judgment.

A provenance page answers the next question

A visible label tells someone that an image was digitally altered. It does not necessarily answer what changed, what the original looked like, or where the asset came from.

A public provenance page gives the listing image a reference point that can travel with the marketing kit. It can help an agent show the relationship between an original listing photo and its staged version, rather than asking a viewer to trust a detached JPEG circulating across several channels.

This matters most when a seller, buyer, or broker asks for verification after the image has left the MLS. The agent should be able to locate the source material without sorting through old downloads, revised files, and multiple folders during a showing week.

The same principle applies to text and video. A narrated listing tour, MLS description, and staged photos should be reviewed as one kit, because each can create a different impression of the property. The provenance record helps preserve the image-specific context that an MLS field cannot carry on its own.

Build the check into your publishing routine

Apollo 13’s team did not solve the canister problem by assuming the two systems would connect. They addressed the interface directly. Listing marketing needs the same discipline.

Before scheduling social posts, open the exact files that will be published and confirm three things:

• The staged version has a readable disclosure in the dimensions being posted.
• The MLS disclosure field is completed where the local MLS requires it.
• The image kit includes a working provenance reference for anyone who needs to verify the original and altered versions.

Keep the original and staged images paired in the same listing folder. Review any crop before it goes live. If a platform forces a crop that compromises the disclosure, prepare a version where the label remains readable instead of hoping the MLS record will supply the missing context.

That extra check is short. It also prevents an upload-night decision from becoming a disclosure problem after the photo has already spread.