Atlasly Vision: AI Rendering Built for Architects, Urban Designers and Planners
What Atlasly Vision does, who it is for, and how its renders, edits, diagrams and flythroughs fit a real design workflow — from first massing to a client-ready report.

Quick answer
Atlasly Vision is the image and video workspace inside Atlasly that turns a written brief, a sketch, or a massing model screenshot into architectural renders, diagrams, maps and short flythrough videos. It ships with fourteen purpose-built tools for architects, urban designers and planners, curated starting points for each discipline, a choice of leading rendering engines, and an iteration loop that carries a result forward — refine it, reroll it, upscale it to print quality, and drop it straight into a site report.
Most image tools are built for everyone, which means they are tuned for no one. Ask a general tool for a dusk exterior and you get atmosphere without architecture: beautiful light, implausible structure, a site that does not exist.
Atlasly Vision starts from the opposite position. It assumes you are working on a real site, with a real brief, for a client or a planning authority who will ask awkward questions. The tools, the starting points and the defaults are all shaped around architectural and planning work — and because Vision sits inside Atlasly, it can draw on the same site context as the rest of your analysis.
What is Atlasly Vision?
Vision is the visualisation surface of Atlasly, available at /vision inside the app. It combines four kinds of capability in one place:
- Renders — photoreal exteriors and interiors from a written brief or a reference image
- Edits — change a render or photo with an instruction, remove objects cleanly, or apply a curated architectural style
- Diagrams and maps — masterplan diagrams, schematic floor plans, site analysis diagrams, figure-ground and sun path studies, and custom map styling
- Output — variations grids for comparing directions, print-quality upscaling, and short cinematic flythrough videos
Everything runs in the browser. There is nothing to install, and no render farm to configure.
What can architects, urban designers and planners each use it for?
The Explore tab organises starting points by discipline, so the first click is already close to your workflow.
Architects typically start with dusk or golden-hour exteriors from a massing model, material studies of a courtyard elevation, or biophilic interiors for client moodboards. Attach a screenshot of the model, describe the atmosphere, and iterate on the same image until the materiality reads right.
Urban designers lean on the aerial masterplan, street-section and map styling tools — illustrative plans that communicate structure, landscape and movement without a day in Illustrator.
Planners use the computed diagrams: figure-ground and sun path studies are generated from real site data rather than imagined, so they are accurate enough to sit in a pre-application document. Site analysis diagrams label sun, wind, views and access for committee-ready context.
How do you write a brief that produces a good render?
Vision rewards the way architects already describe buildings. A short, specific brief beats a long vague one, and the composer helps you build it:
- Refinement chips add camera angle, light, season, atmosphere, materials and entourage with one tap — aerial view, golden hour, board-marked concrete, people on the pavement
- Exclusions let you state what to leave out — no cars, no scaffolding, no people
- Framing and batch controls set the aspect ratio (including 21:9 for presentation boards) and how many options to generate at once
Every tool remembers its own settings, so your interior renders stay portrait and your exteriors stay widescreen without re-setting anything.
Which rendering engines does Vision use?
Vision routes each tool to a chain of leading engines — including Flux 2 Pro, Nano Banana 2, GPT Image, Gemini, Recraft, Imagen, SeedVR and Kling — and falls back automatically if one is unavailable, so a run succeeds rather than erroring.
You can leave the picker on Recommended and never think about it. If you do want control, the picker groups engines into Best quality and Fast & lighter tiers, with a simple $ to $$$ symbol showing how heavy each one is. Expensive does not always mean better for a given task — a fast engine is often the right choice for early iteration, with a quality engine reserved for the image that goes in front of the client.
How does the iteration loop work?
A render is rarely right first time, so every result in Vision carries its own next steps:
- Use as source feeds the image back into the editor, so you refine the same view instead of starting over
- Reroll runs the same brief with fresh variation when the composition is right but the detail is not
- Upscale takes a chosen result to print quality at 2x or 4x
- Copy description lifts the exact brief for reuse across a set of images
The workspace view goes further: brush over a region to change only that area, hold the geometry with a preservation dial, compare two directions with a slider, and see exactly how each image was made — brief, settings and lineage included.
How does Vision connect to the rest of Atlasly?
This is where Vision differs from a standalone image tool. When you work inside a project, Vision knows the site you are analysing — the composer's site chip shows the address and local authority it is working from, and that context shapes the output.
Finished images do not sit in a downloads folder. Add to Report and Add to Pack place them into the same evidence pack as your constraints mapping, flood risk and planning analysis, so the visual and the argument travel together. A figure-ground study, a massing render and a constraints map can all come from one workspace, about one site.
How do you get started?
Open Vision from the Atlasly app, pick a starting point from the gallery that is close to what you need, adjust the brief, and generate. The whole loop — brief, generate, refine, upscale, file into a report — takes minutes rather than days.
Illustrative example
A small practice preparing for a client meeting on a tight infill site needed a credible dusk exterior from an untextured massing model, a figure-ground diagram for context, and a streetscape view with the parked cars removed. Using Vision, the team attached the massing screenshot, worked from the dusk-exterior starting point, and refined the same view through three instruction edits rather than three re-renders. The figure-ground came from site data rather than a traced approximation, and the finished images were added to the pre-application pack the same afternoon. (Illustrative scenario.)
Frequently asked
What is Atlasly Vision?
Atlasly Vision is the image and video workspace inside Atlasly. It turns a written brief, sketch or massing model screenshot into architectural renders, diagrams, maps and short flythrough videos, with tools designed for architects, urban designers and planners.
Can I use my own images, sketches or model screenshots?
Yes. Attach a reference image or paste a link and Vision works from it — editing with instructions, applying a style, removing objects or upscaling. A preservation dial controls how closely the output keeps your original geometry.
Which rendering engines can I choose from?
The picker offers a Recommended default plus a choice of leading engines grouped into Best quality and Fast & lighter tiers, including Flux 2 Pro, Nano Banana 2, GPT Image, Gemini, Recraft V4 Pro, Imagen 4 Ultra, SeedVR 2 and Kling 3 Pro. Expense is shown with a simple $ to $$$ symbol.
Can Vision output go into planning documents?
Yes. Results upscale to print quality and can be added directly to an Atlasly report or evidence pack. The computed tools — figure-ground and sun path studies — are generated from real site data, which makes them suitable for planning conversations.
How is Vision different from a general image generator?
Vision is built around design work: discipline-specific tools and starting points, camera and material language architects actually use, site context from the wider Atlasly analysis, and an iteration loop that refines one image rather than generating endless disconnected ones.
Conclusion
Good visualisation is not about producing more images. It is about producing the right image early enough to improve a decision — and being able to stand behind it when the client or the case officer asks where it came from.
Atlasly Vision keeps that loop inside the same workspace as your site analysis, so the picture and the evidence never drift apart. Open /vision, start from a template, and see how far one well-briefed image can go.

About the author
Shatakshi Patil
Architect writing about pre-construction due diligence, planning context, and site intelligence workflows for design teams using Atlasly.
Sources and references
Authoritative references for the planning policies, regulations, and standards referenced in this article. Always check the publisher for the latest version.
Related articles
Auto-suggested
AI tools UK architects
AI Tools for UK Architects: A Practical Evaluation Guide (2026)
Evaluate AI tools for UK architecture by task, source quality and review effort. Compare site research, early design and documentation without unsupported rankings.
Read
architectural concept renders from site context
From Massing to Render: Using Site Context to Improve Early Design Visualisations
How architects can use site intelligence and contextual inputs to produce more credible early concept visuals before design development.
Read
architectural concept renders from site context
How to Create Architectural Concept Renders That Still Respect the Site
How to create architectural concept renders grounded in real site context, covering orientation, topography, neighbouring scale, and review checks that keep early visuals honest.
Read
planning constraints UK architects
Understanding Planning Constraints Before You Design: A Guide for UK Architects
A UK-focused guide to reading planning constraints early, from conservation and flood overlays to Article 4, heritage, and policy triggers.
Read