Prince William County, VA zoning › where can I put this

Where can I put a manufacturing of musical instruments and toys in Prince William County, VA?

Prince William County, VA, excluding the incorporated towns, which run their own zoning.

Manufacturing of musical instruments and toys

Allowed only with a discretionary approval in 2 districts

These require a hearing or an approval from the county. They are not a “no”, and they are not a “yes” either.

District	Properties loaded	Code	What says so
MXD-U the ordinance paragraph quoted here	4 20109 (4)	Conditional	Sec. 32-307.33 item 7 Manufacturing of musical instruments and toys.
O(F) the ordinance paragraph quoted here	4 20109 (1), 22192 (3)	Conditional	Sec. 32-402.43 item 10 Manufacturing of musical instruments and toys.

This part is the paid tier: the property list behind these counts. Everything above it on this page is free and carries the ordinance section and quote it came from.

Cancel anytime. You keep access until the end of the month you paid for. Access is remembered in this browser on this device only — there are no accounts, so opening a different browser will not carry it over. Lost it? Email us and we will re-issue.

This answer is good through September 9, 2025 — that is the date the ordinance we hold runs to, as published by Municode (Prince William County Code). We last checked with the county on September 24, 2026 and found nothing newer. That is a check on that date, not a promise about today.

Ask another one in Prince William County, VA

What this does not cover

157,019 properties are loaded, in 21 ZIP codes (20109, 20110, 20111, 20112, 20119, 20136, 20137, 20143, 20155, 20169, 20181, 20187, 20198, 22025, 22026, 22125, 22134, 22172, 22191, 22192, 22193). Properties outside those ZIPs are not counted here at all. A further 553 carry no street address in the county’s own parcel record, so they fall in no ZIP above — they are still loaded and still counted in the 157,019.
A further 76,146 properties carry a parcel zone code this page cannot match to a single column of the use table: (none), A (73 variants, e.g. A-1;A-1C), B (35 variants, e.g. B-1;CTY;M-2), CTY;M (3 variants, e.g. CTY;M-1), CTY;PBD, CTY;PMR, CTY;R (5 variants, e.g. CTY;R-4), FED, FED;PMD;PMR, FED;TWN, M (19 variants, e.g. M-1;M-2), M/T;O(F), M/T;PBD, O(L);R and 22 more.
1,503 of those lie in TWO OR MORE districts at once. Their code below holds every district the parcel really shares area with, joined by a semicolon — A-1;A-1C, A-1;B-1, A-1;B-1;CTY;M-1;M-2;M/T;PBD;R-4, A-1;B-1;M-1, A-1;B-1;M-2 and 188 more. The ordinance does not say the larger share wins, so we do not pick one: the parcel is shown as straddling and is not counted under either district.
48,352 of those carry a code that looks like one of the districts above and is not one. A-1C, R-2C, R-4C, RPC, SR-1C — these are separate zone classifications in their own right, not the same zone with something added, and the use table has no column for them. We do not fold them in.
(none) above means a parcel with no zone code assigned in the county's own data — 4 of them.
Owner filters. We have an owner of record for 153,901 of Prince William County’s 157,019 parcels, of which 18,081 are owned by a company, trust or other organization, including 1,513 owned by public bodies — governments, authorities, schools, churches. That split is Zonescore’s reading of the owner’s name, not something the county published, and we keep the two apart rather than deciding for you which counts as an investor. 5,099 have an owner whose mailing address is outside VA — the county publishes the owner’s state as its own field, so this is its answer rather than our reading of an address. It carries one for 153,880 of them; the rest are not counted either way. 29,429 are owned by somebody this county writes to at a different address — not the property itself. That is where the tax bill goes, which is not the same as where the owner sleeps — an owner can collect mail at a property they rent out, and one who is written to elsewhere may still live here. We can tell you the two addresses differ; we cannot tell you the owner does not live at the property. 24,825 of them are written to an address inside VA, so the out-of-state filter above cannot see them at all. That count is out of the 147,525 properties where we could compare the two addresses. On 6,376 more we could not — the owner is written to a post-office box, or the county’s own record of the property names a street and no building number — and those are left out rather than counted as living at home. Matching two addresses is Zonescore’s reading, not something the county published: we treat “123 Main St” and “123 Main Street” as one place, ignore an apartment number, and compare the ZIP code rather than the town name — a jurisdiction’s record of a property and its record of that property’s owner often name the same place by different towns, and treating those as two addresses would count somebody living in their own house as an absentee. Owned for (based on the last recorded transfer): under 2 years 20,000+; 2-5 years 26,000+; 5-10 years 40,000+; 10-20 years 35,000+; 20-30 years 15,000+. 30+ years: Not offered here. The conveyance records we hold for Prince William begin in about 1995, so they cannot show a 30-year hold. The county sales file we have asked for would close this. 17,000+ properties have no transfer date we can read and are in no bucket.
Owner data from Prince William County's real estate records, retrieved October 2, 2026.
554 of the properties above are listed as “no ZIP in the county’s record” in the ZIP breakdowns. 553 carry no street address at all in the county’s data and 1 carry a street but no city or ZIP — so we cannot place them in a ZIP, and we do not guess one. They are still counted in the district totals.
Overlay districts are not modeled here. An overlay can change what a property allows.
Some cells in this ordinance state two outcomes without saying what separates them; those are shown with their code and their source, and not guessed at.

Built from scripts/build_reverse_index.py, generated 2026-10-11T20:59:04+00:00.