Structure you can read
Roads, regions, plots and masses remain distinct parts of the urban model.
iCity
Procedural city creation
From a road plan to a city you can keep changing.
iCity turns street structure into connected blocks, plots, massing, materials and urban detail—so you can work at city scale without giving up control of the plan or the look.
Structure first · Visual identity second · Both remain editable
Content requiredICITY-HERO-01
Hero render or 8–12 second loop
A city that reads at every scale
Create one cinematic master view of a complete district. The road hierarchy, block structure and material identity should read from the aerial scale, with a human-scale foreground proving finish quality. No interface, labels or generic sci-fi styling.
16:10 display · 2560 × 1600 px · derive 21:9 campaign crop/marketing-shots/icity-hero-01.*
StructureRoads → regions → plots → massing
IdentityMaterials and props as a reusable system
ControlPlan and appearance remain independent
The city as a system
Every visible result begins with structure.
iCity does not begin by scattering buildings. It begins with the relationships that make an urban place legible, then carries those relationships from planning logic to visual character.
Content requiredICITY-SYSTEM-01
Exploded system render
The city, separated into its working layers
Create an exploded axonometric of one finished district: road graph at the base, regions and plots above it, building massing, then the dressed city. Use one locked camera and Parametra colours for layer separation.
16:10 · 2400 × 1500 px · transparent master also required/marketing-shots/icity-system-01.*
Rules you can steer
Change the decisions that shape the city instead of repairing a frozen result.
Output you can continue
Keep editing, dressing and presenting the city after its first generation.
One connected workflow
Four moments from linework to place.
Begin with a road idea, develop the urban fabric, give it character and keep revising. Each step carries the same project forward so decisions remain connected.
Content requiredICITY-WORKFLOW-01
Workflow visual
Draw the network
A clean product capture showing a real road graph being drawn over light site context. Keep the interface legible, the cursor action obvious and the city area large enough to understand.
Product capture · 4:3 · 1800 × 1350 px/marketing-shots/icity-workflow-01.*
01 / Road structure
Draw the network
Lay out the streets and shape the hierarchy that will organise everything around them.
Content requiredICITY-WORKFLOW-02
Workflow visual
Resolve the fabric
A three-state render or short loop: road graph, resolved plots, then building massing. Use the same camera for every state so the transformation is unmistakable.
3-state render · 4:3 · 1800 × 1350 px/marketing-shots/icity-workflow-02.*
02 / Blocks, plots, massing
Resolve the fabric
Regions close, plots divide and building masses rise from the logic of the plan.
Content requiredICITY-WORKFLOW-03
Workflow visual
Give it character
A street-level render that clearly shows coordinated façades, paving, road markings, vegetation and street props. The result should feel authored rather than random.
Street render · 4:3 · 1800 × 1350 px/marketing-shots/icity-workflow-03.*
03 / Theme and assets
Give it character
Apply materials, props, markings and surface detail as one reusable visual system.
Content requiredICITY-WORKFLOW-04
Workflow visual
Change the decision
A before-and-after comparison from one locked camera. Highlight a meaningful plan change and show the dressed city resolving around it without changing the art direction.
Before / after · 4:3 · 1800 × 1350 px/marketing-shots/icity-workflow-04.*
04 / Edit and resolve again
Change the decision
Move a road, split a plot or revise massing while the city keeps its visual language.
Built for iteration
A product story told through the work.
Structure, visual identity and iteration stay connected across the project, so the city can evolve without losing the decisions that give it coherence.
01 / Structure
Shape an urban system, not a pile of objects.
Roads establish the hierarchy. Regions, lots and building masses resolve around them as connected parts of the same model. The result stays readable enough to select, inspect and direct.
- Road and junction editing
- OpenStreetMap starting points
- Region, plot and building resolution
Content requiredICITY-FEATURE-01
Product proof
The editable city model
An oblique product render with roads, regions, plots and massing colour-coded as distinct layers. Include a restrained UI edge or selection highlight to prove editability without turning this into a software screenshot.
Hybrid product render · 16:10 · 2400 × 1500 px/marketing-shots/icity-feature-01.*
02 / Visual system
Build a look that belongs to the whole place.
Describe a direction, review the guides, then build a theme that coordinates materials and props across the district. Reuse what belongs to the project, replace one weak asset, or redirect the whole visual language without rebuilding the urban structure.
- Prompt, guides and approval
- Reusable prop and material libraries
- Targeted regeneration
Content requiredICITY-FEATURE-02
Product proof
One district, two coherent themes
A precise split-screen of the same street and camera in two art directions. Geometry must match exactly; only materials, props, vegetation and atmosphere should change.
Matched render pair · 16:10 · 2400 × 1500 px/marketing-shots/icity-feature-02.*
03 / Iteration
Keep designing after the city appears.
Draft and Design remain separate, so a late planning decision does not force a new visual project. Refine structure and appearance independently, then resolve them together again.
- Plan and theme remain independent
- Semantic lanes and markings
- Project versions for meaningful milestones
Content requiredICITY-FEATURE-03
Product proof
A real revision, carried through
A four-panel sequence from a single project: original street, edited alignment, updated plots and final re-dressed result. Use annotations sparingly to identify the changed decision.
4-panel sequence · 16:10 · 2400 × 1500 px/marketing-shots/icity-feature-03.*
The render wall
A city generator should be judged by its cities.
From the district scale to the pavement edge, the same underlying system holds together across different densities, atmospheres and terrains.
One visual language / many urban conditionsContent requiredICITY-RENDER-01
Final-quality city render
Waterfront district master view
Wide aerial at late afternoon. Show a complete road hierarchy, mixed building scale, waterfront edge and enough foreground detail to communicate finish quality.
Hero render · 21:9 · 3200 × 1370 px/marketing-shots/icity-render-01.*
Content requiredICITY-RENDER-02
Final-quality city render
Dense centre from above
High oblique view focused on connected blocks, varied plots and a legible street network. Avoid fog or effects that hide the procedural structure.
Aerial render · 3:2 · 1800 × 1200 px/marketing-shots/icity-render-02.*
Content requiredICITY-RENDER-03
Final-quality city render
Human-scale street life
Eye-level view with façades, pavement, markings, vegetation and props all visible. Include people only for scale; the generated place remains the subject.
Street render · 3:2 · 1800 × 1200 px/marketing-shots/icity-render-03.*
Content requiredICITY-RENDER-04
Final-quality city render
Low-rise neighbourhood
Calm daylight view of smaller plots, residential massing and landscape. Show that the system handles more than dense city-centre imagery.
District render · 3:2 · 1800 × 1200 px/marketing-shots/icity-render-04.*
Content requiredICITY-RENDER-05
Final-quality city render
Night identity study
The same authored quality after dark: readable streets, restrained lighting and a distinct material direction. Avoid generic neon or science-fiction styling.
Night render · 3:2 · 1800 × 1200 px/marketing-shots/icity-render-05.*
Content requiredICITY-RENDER-06
Final-quality city render
Terrain and green structure
A district meeting visible terrain, parks and green buffers. Make the relationship between built fabric, slope and landscape easy to read.
Landscape render · 3:2 · 1800 × 1200 px/marketing-shots/icity-render-06.*
Where iCity fits
Different briefs. The same city-scale problem.
Planning teams, visualization studios and digital production groups can begin from the same structured city and take it toward different outcomes.
Content requiredICITY-USE-01
Use-case render
Planning and urban design
A professional planning scene with two massing options for the same site, seen from one camera. Emphasise clarity of comparison rather than presentation effects.
4:3 · 1800 × 1350 px/marketing-shots/icity-use-01.*
Planning and urban design
Compare structure, density and massing while the plan is still open to change.
Content requiredICITY-USE-02
Use-case render
Architecture and visualization
A designed building or development in focus with a coherent generated district around it. The context should support the architecture without looking like a generic background plate.
4:3 · 1800 × 1350 px/marketing-shots/icity-use-02.*
Architecture and visualization
Build credible city context around the site that is receiving the detailed design effort.
Content requiredICITY-USE-03
Use-case render
Simulation and digital production
A clean technical render showing a complete urban environment with readable lane, block and building structure. No unsupported simulation overlays or fictional analytics.
4:3 · 1800 × 1350 px/marketing-shots/icity-use-03.*
Simulation and digital production
Start with structured streets and districts instead of placing the urban world object by object.
Keep the valuable parts
The result is more than the final picture.
The road logic, editable urban structure and reusable visual assets remain useful after the first presentation. That is what makes iCity a working system rather than a one-off image generator.
Background image briefICITY-CTA-01
The city at presentation scaleA wide, calm final render of the hero district at blue hour. Reserve clean dark space on the left for the message and keep the strongest building cluster on the right.
Background render · 3:1 · 3000 × 1000 px · /marketing-shots/icity-cta-01.*Start with the road plan
Build a city you can keep designing.
Request access to iCity, or bring us the urban workflow you need to solve.