I get asked this more often than I expected. Someone uploads a floor plan or a set of property photos, then messages me asking if they can put it on their own site without downloading and re-uploading everything. The answer is yes. That’s what the embed feature is for, and it’s been part of Freesaweria for a while now. It just wasn’t obvious unless you went looking for it.
This page is a straightforward walkthrough. No jargon, no assumptions about what you already know. I’m writing it the way I’d explain it to a builder in Thane who just wants his listing photos to show up properly on his own webpage.
What embedding actually means here
When you embed an image or a tour from Freesaweria, you’re not copying the file. You’re placing a live version of it on another page — your property listing site, your blog, a shared client presentation, wherever. The visual stays hosted on our servers, loads fast, and updates if you replace the source file later. No broken links, no emailing heavy attachments.
This matters more for real estate than it did when the site was just a general upload tool. A floor plan embedded on a listing page stays sharp. A 360-degree tour embedded in a WhatsApp share link opens without the client downloading an app. The hosting handles the heavy lifting.
What you can embed right now
- Single property photos — exterior shots, room-by-room interiors, balcony views
- Floor plan sketches and 2D layouts
- Side-by-side comparison sliders — useful for before-and-after renovation shots
- 360-degree photo spheres — the interactive kind where you drag to look around a room
- Full albums or curated galleries — like an inspection board for a single property
Virtual walkthroughs and multi-room tours are in testing. If you have access to those, the embed process is the same. If you don’t see the option yet, it’ll show up when it’s ready for your account.
How to get the embed code
Open any image, album, or tour you’ve uploaded. On the right side of the screen — or below the visual on mobile — there’s a share panel. It lists a direct link, a short link, and an embed option. Click the embed option. You’ll see a snippet of HTML code.
Copy that entire snippet. Don’t trim it, don’t edit out parts that look unnecessary. The code includes the container size and a fallback link for platforms that strip embeds. It’s short, usually three or four lines.
Paste the snippet into the HTML of the page where you want the visual to appear. If you’re using a property listing platform that has a custom HTML block or a source editor, use that. If you’re pasting into a WordPress post, switch to the text editor first. Most website builders — Wix, Squarespace, Blogger, whatever — have an embed block or an HTML widget. Use that.
Embedding on Indian property portals and listing sites
Not every portal allows third-party embeds. Some strip iframe tags, some only accept images uploaded directly to their own servers. I’ve tested this on a handful of common platforms used in Mumbai, Pune, and Bangalore real estate circles.
For portals that accept custom HTML in the description field, the embed works without issues. The photo or floor plan renders inline, and it scales to the width of the listing container. For portals that block external embeds, use the direct link from the same share panel instead. It opens the visual in a new tab, hosted cleanly on Freesaweria with no clutter around it.
If you’re sending property visuals to clients over WhatsApp or email, the short link is usually better than an embed. It loads faster in a mobile browser and doesn’t require the client to be on a specific page to view it. I keep both ready — embed code for the official listing, short link for quick sharing.
Floor plans deserve special attention
I learned this the hard way. A floor plan embedded at the wrong size is useless. If the embed container is too narrow, the room labels become unreadable. If it’s too large on mobile, the viewer has to pinch-zoom and scroll around, which defeats the purpose.
For floor plans, I set the embed width to at least 700 pixels on desktop layouts. On mobile, the responsive code in the snippet handles scaling down, but the original upload needs to be high-resolution enough to stay legible when shrunk. I upload floor plans at 1600 pixels wide minimum. The file size stays manageable because the image is mostly line work and text, not a dense photograph.
If your floor plan includes dimensions or room labels in small text, test the embed on a phone before sending the listing live. Open the page on your own device, check if you can read the labels without zooming. If not, re-upload a larger version and replace the file. The embed link won’t change, so you won’t need to update the code on your listing page.
360-degree tours and interactive embeds
These work differently from static images. The embed code for a 360-degree photo sphere includes a lightweight viewer that loads alongside the image. It adds maybe half a second to the page load time. On a fast connection, it’s imperceptible. On a slow mobile network, the static preview loads first and the interactive layer kicks in a moment later.
The viewer lets the person drag to rotate the view, pinch to zoom, and click hotspots if you’ve added any. All of that runs inside the embed container. You don’t need to configure anything extra. Just paste the code and it works.
One thing worth knowing: some listing platforms cache their pages aggressively. If you replace a 360-degree tour file with an updated version, the embed might show the old one for a few hours until the cache clears. Adding a random parameter to the embed URL forces a refresh, but that’s a slightly more technical step. If you need to do that, the support contact is at the bottom of this page.
What the person viewing the embed sees
They see the visual, hosted on Freesaweria, loading inside your page. There’s a small watermark in the corner — unobtrusive, doesn’t cover the content. If they click the visual, it opens the full version on Freesaweria in a new tab. From there they can zoom further, download if you’ve enabled downloads, or browse the rest of the album if it’s part of one.
There’s no advertising on the embedded view. No pop-ups, no banners. The experience is clean. That’s deliberate. A property listing with ads around the photos looks unreliable, and that’s bad for everyone involved.
Things that go wrong and how to fix them
Embedded visual doesn’t load — Check if the original file is still on Freesaweria. If you deleted it or set the album to private, the embed breaks. Make the album public or unlisted, not private. Unlisted means it’s hidden from search but accessible to anyone with the link or embed code.
Embed works on desktop but not mobile — Usually a container width issue. If your page has a fixed-width layout that doesn’t adapt, the embed might overflow or get cut off. The fix is on your page’s CSS, not on the embed code. But as a quick workaround, you can wrap the embed snippet in a div with max-width set to 100%.
Portal blocks the embed entirely — Use the direct link instead. It’s not as seamless, but it’s reliable. Some portals have whitelists for embed sources. If you want Freesaweria added to a specific portal’s whitelist, let us know. We can’t guarantee they’ll do it, but we’ll reach out.
Embedded visual looks blurry — The original upload resolution is too low. Re-upload at a higher resolution. For photos, 2000 pixels on the long edge is a safe target. For floor plans and sketches, go larger. The hosting compresses intelligently, but it can’t invent detail that wasn’t there in the original file.
A note on load speed and page performance
Embedding ten high-resolution photos on a single listing page will slow it down. That’s true regardless of where the images are hosted. I recommend embedding three to five key visuals — the hero shot, the floor plan, maybe a 360-degree tour — and linking to the full gallery for the rest. The page stays fast, the client sees what matters, and the detailed viewer can browse everything else in one click.
Our servers are in India, which helps with load times for Indian audiences. If your listing targets NRI buyers or international property investors, the visuals still load quickly because the files are optimized on upload. I’ve tested embeds on pages accessed from Dubai, Singapore, and London. The difference in load time compared to locally hosted images is negligible for standard listing photos.
Why I still use embeds instead of uploading everywhere
I manage visuals for multiple property listings across different platforms. Uploading the same set of photos to five different sites means updating five different places if something changes — a floor plan gets revised, a room gets repainted and re-photographed, a price tag on a layout needs removal. With embeds, I update the file once on Freesaweria and every listing that uses the embed reflects the change. That alone saves me hours every month.
There’s also the consistency. A floor plan hosted and embedded from the same place looks identical whether someone views it on a builder’s site, a broker’s listing, or a shared link in a family WhatsApp group. The quality doesn’t degrade because someone screenshotted and re-uploaded it three times.
If you run into something not covered here, or if your setup is unusual and you’re not sure how to make embeds work, reach out directly. I’m not on a support rotation or anything formal — I just answer messages from people using the platform. My contact is in the footer of the site.
— Ananya