Home Architect
Turn a map location or an empty plot into a measured floor plan, then check it against building rules, watch the sun move across it, walk through it in 3D, and price the build — all in the browser, with nothing uploaded.
Loading tool…
From a map pin to a costed floor plan, without a server
Designing a house starts with two things: a piece of land, and where north is. Everything downstream — which rooms get the morning sun, where the shadows fall in winter, how much wall you have to build — follows from those. Home Architect starts there. Paste a Google Maps link or type an address and the map centres on the spot; the coordinates are pulled straight out of the URL, so no mapping account or API key is involved. Building outlines come from the OpenStreetMap Overpass API, which returns real mapped footprints as polygons. If nothing is mapped where you are — common outside dense cities — switch to the satellite layer and click the corners of the plot yourself. Corners stay draggable, and the area and perimeter update as you move them.
That polygon is then projected onto a local tangent plane: metres east and metres south of the plot's own centre. Over a plot the error against a proper geodetic projection is a few centimetres, far below anything that matters for drawing walls. From that point on the drawing is in real metres, and the blueprint canvas is a true scale drawing rather than a sketch.
Rooms are not something you declare. They are worked out from the walls: every wall is split wherever another crosses it, endpoints within three centimetres are welded onto shared nodes, and the minimal cycles of the resulting planar graph are the rooms. Each connected group's largest cycle is its outline and is discarded; what remains are the enclosed spaces. That is why closing a gap in a wall instantly produces a room with an area, a name, a floor finish and a cost — and why leaving one open produces nothing.
The sun model is the standard NOAA approximation: day-of-year gives the solar declination and the equation of time, longitude and the clock give the hour angle, and from those come the altitude and the azimuth. Shadows on the plan are the wall footprints swept away from the sun by height divided by the tangent of the altitude. Direct sun per room is a different question and is answered separately: for every half hour of daylight, each window is tested for whether it faces the sun at all, and then a ray is cast towards the sun to see whether another part of the building is in the way.
Why we built this tool
Architectural software is either expensive, cloud-locked, or both, and the free web planners tend to want an account before they will show you a wall. None of that is necessary. A browser can already read a folder, do the astronomy, run the geometry and render WebGL, so a planning tool that never uploads a thing is perfectly possible — and for property data it is the right default. Where you live, what your plot looks like and what you can afford to build are nobody else's business.
The parts most people cannot do in their head are the ones we automated: whether a room is legal, whether the corridor is wide enough to carry furniture, whether the bedroom you put on the north side will ever see the sun, and what the whole thing might cost. The checks cover the common residential minimums — room areas, corridor and door widths, ceiling height, escape windows, the one-to-ten glazing rule, door swing clashes, bed clearance, the kitchen work triangle — and each finding says what the value is, what it should be, and where it is. Several offer a one-click fix.
It is a design and feasibility tool, not a substitute for a professional. It will tell you that a 7 m² bedroom is under the usual 9 m² minimum and that your hallway is 80 cm wide; it will not tell you the local code, the ground conditions, or what your municipality will approve. Drawings still need an architect or engineer to sign them off, and the estimate is a regional average, not a tender.
Getting good results
- If OpenStreetMap has nothing mapped at your address, do not fight it — press Satellite, then Trace plot, and click the four corners. It takes ten seconds and is usually more accurate than the mapped parcel anyway.
- Set the north rotation before you judge any sun result. It is under Properties with nothing selected, and every shadow, sun-hour figure and orientation score depends on it.
- Type while you draw: with the wall tool active, type
4.5and press Enter to commit a wall of exactly that length in the direction you are pointing. Hold Shift to invert the angle lock. - Rooms are named by dropping a room tag inside them, which the rectangle tool does for you. If a space shows as “Room” with a guessed type, click it and set the type — the type drives the minimum-area check, the floor finish and the cost per square metre.
- The auto-layout is a starting point, not an answer. Generate, then drag the walls: everything downstream — areas, checks, sun hours, quantities, the 3D model — recalculates as you move them.
- Sun hours are only as good as your windows. A room with no windows reports zero hours because it genuinely gets no direct sun, not because the maths failed.
Quick start: designing a house in Home Architect
- Open Site & plot and paste a Google Maps link, type an address, or press the crosshair to use your current position.
- Press Import OSM footprint to pull mapped outlines, or Satellite then Trace plot to click the corners yourself. Drag any corner to correct it.
- Press Use as site. The plot drops onto the blueprint canvas at true scale, in metres.
- Either describe the house in the Auto-layout tab (“3 bedrooms, 2 bathrooms, open-plan kitchen, south-facing balcony”) and press Generate, or draw walls yourself with the wall and room tools.
- Add doors and windows by clicking the wall they belong in, then drop furniture to test that the rooms actually work.
- Open Checks and clear the red items. Open Sun, set the date, and drag the time slider or press Play the day to watch the shadows move.
- Switch to 3D & AR to walk through it, and read the running total in Cost. Export the plan as SVG or PNG, the estimate as CSV, and the model as OBJ.
Everything — the map tiles you look at aside — happens in your browser. Projects are saved to this browser's own storage, and the .json export is your backup. There is no account, no upload, and no copy of your property on anyone's server.
Getting the land in
There are four ways in, and they all end at the same polygon.
| Input | What happens |
|---|---|
| A pasted Google Maps link | The coordinates are read straight out of the URL (@lat,lng, !3d…!4d…, q=lat,lng) |
| An address | Geocoded through OpenStreetMap's Nominatim, with suggestions as you type |
| A click on the map | Drops a draggable pin wherever you want it |
| A KML or GeoJSON file | The first polygon in the file becomes your plot |
There is no Google Maps API key anywhere in this, because there is no server to keep one on. A public key in a page anyone can view is a key anyone can bill, so the tool takes the honest route: it parses the link you already have, and gets everything else from OpenStreetMap and Esri's open satellite imagery.
For the outline itself, Import OSM footprint queries the Overpass API for way["building"] and relation["building"] within 80 metres, and falls back to land-use and parcel boundaries within 250 metres when nothing is mapped. You get every candidate as a clickable polygon with its area on the tooltip. When OpenStreetMap has nothing — which is normal outside dense cities — switch to satellite and click the corners yourself. Corners stay draggable, right-click removes one, and the area and perimeter update as you drag.
Press Use as site and the polygon is projected onto a local tangent plane: metres east and metres south of the plot's own centre. Over a residential plot that is accurate to a few centimetres, which is an order of magnitude below anything that matters when you are drawing walls.
Rooms you don't have to declare
Most planners make you draw a "room" object. This one doesn't have the concept. You draw walls; the rooms are derived.
Every wall is split wherever another wall crosses it. Endpoints within three centimetres are welded onto shared nodes. The result is a planar graph, and the minimal cycles of that graph — traversed by always taking the tightest turn at each node — are its faces. Each connected group's largest face is the outside of the building and is thrown away. What is left are the enclosed spaces, with their polygons, areas, perimeters and bounding walls.
That has a consequence worth knowing: close a gap and a room appears instantly, complete with an area, a name, a floor finish and a line in the estimate. Leave a gap and you get nothing, because there genuinely is no room there yet. The checks panel says so in as many words rather than failing silently.
The same derivation powers a subtler measurement: the widest circle that fits inside a room. That is the honest answer to "how wide is this space", and it is what the 90 cm corridor rule is checked against.
Where the sun actually goes
The solar engine is the standard NOAA approximation. Day of year gives the declination and the equation of time; longitude and the clock give the hour angle; from those come altitude and azimuth. Shadows on the plan are each wall's footprint swept away from the sun by its height divided by the tangent of the sun's altitude — the same arithmetic a surveyor does with a stick.
Direct sunlight inside a room is a different question, and the tool answers it separately. For every half hour between sunrise and sunset it takes each window in the room's own walls, works out the direction that window faces (outward, away from the room's centroid), and checks whether it points at the sun at all. If it does, a ray is cast towards the sun and tested against every other wall — if something taller than the shadow line is in the way, that window is not lit. Add it up and you get the number that actually matters: this bedroom gets 2.5 hours of direct sun on 21 December, from the south-east.
Drag the time slider, or press Play the day and watch the shadows swing across the plan. Turn on the daylight heat map and every square metre is coloured by the share of the day it spends out of shadow — which is how you find out that the terrace you planned is in shade from two o'clock.
The checks are boring, which is the point
Real building codes are local and change. What does not change much is the set of things that are wrong in every jurisdiction: bedrooms under 9 m², corridors under 90 cm, doors under 80 cm clear, ceilings under 2.4 m, a bedroom with no openable escape window, a habitable room with less than a tenth of its floor area in glass, a door that opens into a kitchen counter, a bed with 30 cm to squeeze past.
Home Architect checks all of those as you draw, colour-codes them red, orange and yellow, and for each one tells you the current value, the required value, and where it is. Several offer a one-click fix — widen the door, flip the swing, raise the ceiling, add a window to an outside wall. The kitchen work triangle is measured. The site coverage against your plot is measured.
It is a sanity check, not a permit. Local code, ground conditions and what your municipality will actually approve are outside anything a web page can know, and the drawings still need a licensed architect or engineer. But going into that conversation with the obvious problems already fixed is worth a great deal.
The layout generator is not a language model
Type "3 bedrooms, 2 bathrooms, open-plan kitchen, office, south-facing balcony" and press Generate. What happens next is a constraint-satisfaction pass, and it is deterministic enough to explain in a paragraph.
The prompt is parsed into a room programme with target areas from a table of standard sizes. The buildable rectangle is found by insetting your plot by the setback and shrinking until it fits inside the boundary, then shrinking again to the area the programme actually needs. That rectangle is sliced recursively by area — public rooms first, so the zones stay contiguous. Then rooms are swapped between slices while the score improves: area fit dominates, so nothing lands in a slot three times its size, and orientation and adjacency choose between the sensible options that remain. Living rooms and bedrooms want south, bathrooms and utility rooms want north, kitchens want the east.
Walls are then built from the slice edges, with the outer ring load-bearing and the internal lines as partitions. Doors come from a maximum-overlap spanning tree rooted at the hall or living room — which guarantees that every room is actually reachable — plus a front door on the public side. Windows are sized on each external edge to clear the one-to-ten glazing rule. Furniture is placed per room type, because a bedroom that cannot hold a bed is not a bedroom.
Then drag it about. The generated plan is ordinary geometry, and everything recalculates as you move it.
Walking through it
The blueprint extrudes to a 3D model on demand: walls split around every opening so the reveals are real, glass in the windows, leaves in the doors, floors per room in the finish you chose, a pitched, flat or skillion roof, and the sun placed as a directional light from the same astronomy the plan uses — so the shadows in 3D are the shadows on the plan. Orbit it, turn the roof off to look inside, or switch to walk mode and move through it at eye height with WASD.
On a phone or headset that supports WebXR, Enter AR puts the model in front of you at 1:1. Standing on your own plot and walking through the front door of a house that does not exist yet is a strange and genuinely useful experience — you find out that the hall is too tight in about four seconds.
Export the model as OBJ, the plan as SVG or PNG, and the estimate as CSV.
What it will cost
Every wall you stretch and every room you close updates a bill of quantities: floor area, net wall area after openings, external versus internal wall length, counts of doors and windows, wet rooms, fixtures. Those quantities are multiplied by a rate table — foundation, structure, roof, external and internal finishes, floors, joinery, plumbing, electrical, HVAC, fixtures, then labour and permits as percentages — and scaled by a regional multiplier and a finish level.
You get a total, a cost per square metre, a category breakdown, a material list you could take shopping, and a short list of ways to spend less that responds to what you actually drew. It prints, and it exports to CSV.
Every rate is an average. Averages are wrong in detail and useful in aggregate: they will tell you whether you are designing a 150,000 house or a 400,000 one, which is the question that matters before an architect's first invoice.
Nothing leaves the browser
The map tiles you look at come from OpenStreetMap and Esri, and geocoding a typed address asks Nominatim — those are lookups anyone can make. Everything else is local. Your plot polygon, your plan, your costs and your saved projects live in your own browser's storage, exported to a .json file whenever you want a backup. There is no account, no upload, and no copy of your property on anyone's server, because there is no server.
Open Home Architect and put your own address in.