What the control sets
The Mixed Use Zone permits residential development alongside commercial and other uses, typically at the edges of activity centres and along main roads. What it does not do is set the numbers a residential zone sets. 4 of the 6 rows below are absences, and they are absences in the ordinance rather than in this page’s reading of it.
| Standard | What it sets | Status | Reference |
|---|---|---|---|
| Maximum building height | A schedule sets it, or nothing does | No standard | Clause 32.04 |
| Maximum storeys | The clause has no storey limb | No standard | Clause 32.04 |
| Minimum lot size for subdivision | The clause sets none | No standard | Clause 32.04 |
| Site coverage | 70% | Discretionary | Table B2-5 / A2-5 |
| Street setback | 4 m to an ordinary street, 6 m to a Transport Zone 2 road, or the lesser neighbour setback — see the table below | Discretionary | Table B2-1 / A2-1 |
| Minimum garden area | The zone is exempt | No standard | Clause 32.04 |
Site coverage and street setback are the deemed-to-comply standards of Clauses 54, 55 and 57, which Clause 32.04-8 applies to dwellings in this zone — not zone requirements, and not a zero commercial frontage: the zone sets no setback of its own. A schedule to the zone can lower the setback or raise the coverage. Assessed as at 29 September 2026 under VC253, VC257, VC267, VC276, VC282, VC300, VC308, VC311, VC315.
| Development context | Minimum setback from the front street |
|---|---|
| An existing building on both abutting allotments facing the same street, and the site is not on a corner | The lesser front wall setback of the two abutting buildings, or 6 m, whichever is the lesser |
| An existing building on one abutting allotment facing the same street and none on the other, and the site is not on a corner | The front wall setback of that abutting building, or 6 m, whichever is the lesser |
| No existing building on either abutting allotment facing the same street, and the site is not on a corner | 6 m for streets in a Transport Zone 2; 4 m for other streets |
| The site is on a corner | The front wall setback of the abutting building facing the front street, or 6 m, whichever is the lesser; with no such building, 6 m for streets in a Transport Zone 2 and 4 m for other streets |
Table B2-1, Clause 55.02-1 and Table A2-1, Clause 54.02-1 (VC315). A schedule to the zone may set a smaller distance; a schedule figure applies only if it is less than the table figure. Side street, Clause 55: Front walls fronting the side street: the setback of any abutting building facing the side street, or 3 m, whichever is the lesser. Side walls: that setback, or 2 m, whichever is the lesser. Side street, Clause 54: The setback of any abutting building facing the side street, or 2 m, whichever is the lesser. Under the Mid-Rise Code (Clause 57, Table E2-1) the setback is 4.5 m from the front street and 3 m from a side street, unless a schedule to the zone specifies a distance. Land Axis draws 6 m when it cannot see the neighbouring buildings or the road’s zone — a conservative assumption, not the standard.
The figure most often quoted as one is the Residential Growth Zone’s default height, usually with a storey count attached that no zone clause states — the commonest confusion about this zone. It is not a MUZ default, not a fallback, and not what a silent schedule resolves to. If a source gives you a MUZ height without naming a schedule or an overlay, it has substituted a plausible number for a missing one.
Where the height on a Mixed Use lot actually comes from
Four places. A schedule to the zone. A Design and Development Overlay. An activity centre zone provision. Or, if the proposal runs down a deemed-to-comply pathway, that pathway’s own fallback — which is a property of the pathway, not of the zone. Under the Townhouse and Low-Rise Code that fallback is 9 m.
The distinction matters more than it looks. A pathway fallback applies to a proposal that elected that pathway. It is not a limit on the land, and quoting it as one would tell a reader their site is capped when it is not.
In practice the height that binds a Mixed Use lot is usually in an overlay schedule rather than a zone schedule — which is why the first step on a MUZ site is to find out what sits over it, not what the zone says. Put an address into the home page search and it will list the controls on the land, which is the step before reading them.
Sources
- Victoria Planning Provisions, Clause 32.04 — Mixed Use Zone
- Victoria Planning Provisions, operative text as at VC315 (VPP ordinance API) — Clauses 32.04, 32.07, 32.08, 32.09, 32.10, 54.02, 55.02, 57.02 and 52.06 re-read in full. PRIMARY SOURCE for every figure on this page.checked 2026-09-29
- VPP ordinance — Clause 55.02. Confirms the B2-x standard numbering and the B2-2 building-height fallback of 9 m / 10 m sloping. PRIMARY SOURCE.checked 2026-07-26
Assessed as at 29 September 2026 under VC253, VC257, VC267, VC276, VC282, VC300, VC308, VC311, VC315.
Related: the Design and Development Overlay is where a Mixed Use lot’s height usually is, and the Residential Growth Zone is the zone this one is most often mistaken for.
Check it on a real site
See what applies to a particular property
This page describes the control in general. To see what applies to a particular property, search its address and read the zone, overlays and controls recorded against it. No account is needed for the search.
This page describes the instrument, not your land. Which controls actually apply to a particular property is settled by the planning certificate for it — a section 10.7 certificate in New South Wales, a planning certificate in Victoria — and by the responsible authority.