# Property Listing Image Workflow from Figma > Prepare consistent, lightweight property listing images for portals, agency websites, email alerts, and social promotion without losing important visual detail. - Canonical page: https://www.hypermatic.com/articles/tinyimage-property-listing-image-workflow-from-figma/ - Published: 2026-10-02T00:00:00.000Z - Updated: 2026-10-02T00:00:00.000Z For related resources, read [the resource directory](https://www.hypermatic.com/resources/llms.txt). The [site index](https://www.hypermatic.com/llms.txt) links to products and current pricing. Article and tutorial Markdown URLs replace the final slash with .md; product Markdown uses /.md. A property launch can require a hero image, gallery sequence, floor plan, map graphic, agent portrait, social tile, and email thumbnail. The same files may then pass through a real-estate portal, an agency CMS, a CRM, and an advertising platform—each with different crops and upload limits. If the team exports one oversized folder and lets every channel improvise, rooms get cropped badly, floor-plan labels turn soft, and stale images remain live after the listing changes. [TinyImage](/tinyimage/) can export and compress controlled sets of images from Figma, but the reliable workflow starts by defining what each image is allowed to communicate. ## Build the listing manifest before the layouts Create one row for every destination and image role. Record the required dimensions or aspect ratio, accepted format, file-size limit, safe crop, source, approval status, and expiry rule. A practical manifest might include: - portal hero and gallery images; - agency website card and detail-page hero; - floor plan at desktop and mobile reading sizes; - map or neighbourhood graphic; - email alert thumbnail; - square and vertical social variants; - agent portrait and agency logo. Keep the property identifier in the manifest and filenames. Street names can change during an off-market campaign, while identifiers remain stable. Also distinguish supplied photography from diagrams created in Figma so nobody treats an edited illustration as documentary evidence. ## Protect accuracy while preparing the images Image optimisation must not make a listing misleading. Do not remove permanent fixtures, expand a room, replace a view, or hide a material defect. If an image is a render, artist impression, indicative boundary, or not-to-scale floor plan, keep the required disclosure visible in every relevant crop. Record the approved source for captions such as bedroom count, orientation, lot size, and availability. Those facts do not belong inside the visual asset pipeline unless an authorised source owns them. If the status changes from “for sale” to “under offer,” update the controlled overlay and regenerate every affected slot rather than editing individual files downstream. This is different from a general [marketplace listing image workflow](/articles/tinyimage-marketplace-listing-image-workflow-from-figma/). Property listings combine documentary photography, regulated or contractual wording, location details, floor plans, and time-sensitive availability. ## Design crops around rooms, not rectangles Mark the visual subject and the areas that can safely be cropped. A wide living-room photograph may need to preserve the relationship between the windows, floor, and adjoining space. A square crop that shows only furniture may be attractive but uninformative. Create explicit wide, square, and vertical frames in Figma. Check that: - verticals remain visually straight; - key architectural features survive the crop; - image order tells a coherent tour rather than repeating one room; - floor-plan labels remain readable on a phone; - maps do not imply an inaccurate boundary or distance; - overlays stay clear of portal interface controls. Avoid enlarging a small supplied photograph simply to fill a large hero. Request a better source or use a layout that respects the available resolution. Upscaling cannot restore evidence that was never captured. ## Choose formats by image type Property photography usually benefits from a photographic web format, while a floor plan with thin lines and small labels may need a different export. Logos may remain vector where the destination supports SVG. Test each category rather than applying one format and quality setting to the entire package. Use TinyImage to export and compress the selected frames in batches. Inspect windows, foliage, brickwork, railings, text labels, and gradients because these details reveal compression damage quickly. Compare at the actual card and gallery sizes, not only at 100% zoom on a large monitor. If a portal recompresses uploads, run a pilot listing through the real upload path. The local file may look excellent and still degrade after the portal resizes it. Keep the smallest source that survives the complete publishing chain rather than chasing the smallest local export. ## Use filenames that survive handoff A useful filename maps back to the listing and slot: `PROP-1842-gallery-03-kitchen-1600x1067-v02.webp` Keep sequence numbers stable once a gallery is approved. Replacing `gallery-03` with a new kitchen image is safer than renumbering every later file and breaking references in the CMS or approval thread. Do not put private access details, vendor names, or unpublished addresses into filenames shared with external platforms. The [ecommerce product image workflow](/articles/tinyimage-ecommerce-product-image-export-workflow-from-figma/) has useful guidance on consistent image sets, but property teams need extra controls for truthfulness, location privacy, changing sales status, and ordered gallery storytelling. ## Review the published result, not just the export folder Before launch, upload a representative set to each destination and check: - gallery order and thumbnail crops; - desktop and mobile hero framing; - floor-plan readability and disclosure text; - portal recompression and colour shifts; - email-client thumbnail scaling; - social preview crops; - correct property, agent, and status mapping; - removal rules when the listing expires or becomes confidential. Ask one reviewer to compare the published page against the manifest and another to check the listing facts. Visual QA cannot confirm that a photograph belongs to the correct property. TinyImage removes repetitive exporting and compression from the workflow. Human owners still need to approve accuracy, disclosure, privacy, and channel rules. When those responsibilities are explicit, the team can publish a lighter, more consistent image package without turning production speed into listing risk.