FENCE RULES – SUFFOLK (CITY), VIRGINIA

OVERVIEW

Residential fences are permitted on private property within City of Suffolk, subject to local regulations. For properties located outside City of Suffolk city limits, fence rules depend on the applicable county, town, city, or governing authority for the property location.

Local residential fence rules appear primarily in the City of Suffolk Unified Development Ordinance, including the ministerial permit procedures, the Historic Conservation Overlay District, the Chesapeake Bay Preservation Area and Resource Protection Area standards, the Floodplain Overlay District, stormwater and drainage standards, water-quality stream-buffer standards, and the accessory-use fence standards in Section 31-701. Related requirements also appear in the City Code, the Public Facilities Manual, city zoning-application materials, pool-barrier materials, and Virginia statewide utility-notice and building-code materials.

This page focuses on typical single-family residential fencing. If the jurisdiction's adopted materials do not state a specific limit or requirement, this page notes that the code does not specify one.

Compiled From the City of Suffolk Unified Development Ordinance, including Sections 31-302, 31-413, 31-415, 31-416.2, 31-611, 31-613, 31-615, 31-701, and Appendix C; the City of Suffolk Code of Ordinances, including Chapter 14, Chapter 34, Chapter 35, and Chapter 74; the City of Suffolk Public Facilities Manual Volume I; the City of Suffolk Public Utilities Facilities Manual Volume II; city fence, zoning-application, pool-fence, and pool-barrier materials; and Virginia statewide building-code, utility-notice, erosion and stormwater, livestock, and division-fence baseline materials as of July 2026.

GOVERNANCE

The City of Suffolk regulates residential fence issues through the Unified Development Ordinance, the City Code, the Public Facilities Manual, zoning and fence-permit administration, building-code administration, stormwater and land-disturbance review, right-of-way review, floodplain administration, Chesapeake Bay Preservation Area review, wetlands review, historic-review procedures, and statewide utility-notice requirements.

The Zoning Administrator and the Planning and Community Development Department administer zoning-permit and UDO compliance functions. The Building Official administers the Virginia Uniform Statewide Building Code through the city's building-code framework. The Department of Public Works administers Public Facilities Manual, land-disturbance, stormwater, drainage, and right-of-way permitting functions.

The Director of Planning and Community Development is identified in the UDO as the Floodplain Administrator for the Floodplain Overlay District. The Wetlands Board administers local wetlands permitting functions. The Historic Landmarks Commission and the Director administer Certificate of Appropriateness review in the Historic Conservation Overlay District where the UDO requires that review.

The City of Suffolk does not publish a single standalone residential fence code. Standard residential fence review is structured through the UDO's fence standards, the ministerial fence / zoning permit framework, the City Code, and site-condition layers such as streets, easements, drainage, floodplain, Chesapeake Bay Preservation Area, Resource Protection Area, wetlands, historic overlay, pool-barrier, and stormwater requirements.

PERMIT AND APPROVAL REQUIREMENTS

• Fence / Zoning Permit: The Unified Development Ordinance treats fence permits as ministerial permits and defines a development permit to include a fence permit. The City of Suffolk publishes zoning-application materials for fences. A standard residential fence is therefore handled through the city's fence / zoning permit workflow, separate from any building-permit exemption.

• Building Permit Baseline: The City Code places construction and related building-code matters under the Virginia Uniform Statewide Building Code. Under the Virginia Uniform Statewide Building Code baseline, application for a building permit and related inspections are not required for fences of any height, unless the fence is required for pedestrian safety during construction or is used as the barrier for a swimming pool. This building-permit exemption does not remove the City of Suffolk fence / zoning permit workflow or other zoning, site, overlay, right-of-way, easement, drainage, floodplain, Chesapeake Bay Preservation Area, Resource Protection Area, wetland, historic, stormwater, utility, pool-barrier, or private-restriction requirements.

• Pool Barrier: A fence used as the barrier for a swimming pool, spa, or similar regulated pool condition is not treated as an ordinary exempt yard fence under the statewide building-code baseline. The City of Suffolk publishes pool-fence and swimming-pool / spa barrier materials for that situation.

• Historic Overlay Review: In the Historic Conservation Overlay District, where exterior appearance of a structure as viewed from any public right-of-way is involved, the UDO states that no permit for erection, alteration, or improvement is issued until a Certificate of Appropriateness has been issued. The addition or deletion of fences or walls is listed as a minor action that may be approved by the Director under the historic-overlay procedures.

• Chesapeake Bay / Resource Protection Area Review: Fences located within a Resource Protection Area may be reviewed administratively without an exception request if the UDO's fence-design requirements are met. The fence must not inhibit or alter surface flow, water must be able to flow under and through the fence unimpeded, the fence must be located to avoid removal of vegetation, and disturbance associated with installation must be mitigated through a Minor Water Quality Impact Assessment.

• Wetlands Review: The City Code lists construction and maintenance of noncommercial fences on wetlands as a permitted activity if otherwise permitted by law and if the structure is constructed on pilings so that the tide can flow reasonably unobstructed and the natural contour of the wetlands is preserved. Wetland use or development outside the listed permitted activities requires a permit application to the Wetlands Board or the commission.

• Floodplain Overlay Review: In any Floodplain Overlay District, all uses, activities, and development must be undertaken only upon issuance of a zoning permit and in compliance with the Floodplain Overlay District, the Virginia Uniform Statewide Building Code, and other applicable ordinances. The Floodplain Administrator reviews permit applications for Special Flood Hazard Area and floodplain compliance.

• Stormwater And Land Disturbance: The Public Facilities Manual states that any project disturbing more than 2,500 square feet inside the Chesapeake Bay Preservation Area or 10,000 square feet outside the Chesapeake Bay Preservation Area must obtain a Land Disturbance Permit, and any land-disturbance project of 1 acre or more must obtain construction general permit coverage. The City Code lists installation, maintenance, or repair of fence and sign posts among activities not required to comply with Chapter 35 unless otherwise required by federal law; broader grading, clearing, excavation, fill, driveway, drainage, retaining-wall, or construction activity connected to a fence project may still be reviewed under the city's stormwater and land-disturbance framework.

• Right-Of-Way Work: The Public Facilities Manual states that work performed within the public right-of-way requires a Right-of-Way Permit. The City Code also establishes an encroachment-permit framework for obstructions or encroachments in, upon, or over streets or other city property.

FENCE PLACEMENT RULES

• Property Lines: The ordinance does not state a setback requirement for standard residential fences from interior property lines; however, fences must be located entirely on the owner's property and must not encroach into rights-of-way or easements.

• Required Side And Rear Yards: In single-family residential districts, a fence or wall not more than 6 feet in height may be located in any required side yard or rear yard other than a required yard adjacent to a street.

• Double-Frontage Or Reverse-Frontage Lots: A fence or wall not more than 6 feet in height may be located in a planting screen / no-access easement adjacent to a street serving a double-frontage or reverse-frontage lot.

• Street-Adjacent Required Yards: Except for the specific double-frontage or reverse-frontage allowance, a fence or wall that creates a solid screen may not exceed 2.5 feet in height in a required yard adjacent to a street. Fences with a uniform open area of 50 percent or more may be erected to a maximum height of 4 feet in those required yards.

• Visibility Areas: No fence or wall may encroach into the visibility triangle. The UDO also requires a Traffic Visibility Zone at street intersections, with no fence, structure, earth bank, hedge, planting, wall, or other obstruction between 2.5 feet and 9 feet above the property-line grade, except for the listed utility-pole, trimmed-tree, open-growth plant, building-appurtenance, warning-sign, and elevated-sign exceptions.

• Drainage Channels: No fence or structure may be constructed across an open drainage channel if it will reduce or restrict the flow of water. The Director may require a watercourse or stormwater management facility to be located within a dedicated drainage easement that provides sufficient width for maintenance.

• Stream Banks: For regulated streams under the UDO water-quality stream-buffer section, no fence may be located closer than 15 feet from the top of the Stream Bank. The section states that this protects streambank plants and prevents flood damage to fencing.

• Resource Protection Areas: A fence in a Resource Protection Area must be designed and located so that it does not inhibit or alter surface flow, allows water to flow under and through the fence unimpeded, avoids removal of vegetation, and mitigates installation disturbance through the required Minor Water Quality Impact Assessment.

• Wetlands: A noncommercial fence on wetlands fits the City Code's listed permitted wetland activities only when otherwise permitted by law and constructed on pilings to allow reasonably unobstructed tidal flow and preserve the natural contour of the wetlands.

• Rights-Of-Way, Easements, And Major Utility Easements: Fences must not occupy public rights-of-way, city property, drainage easements, utility easements, access easements, or major underground utility easements except where the applicable city approval or easement terms allow the placement. In major underground utility easements outside the public right-of-way, the UDO prohibits obstruction by new structures, plantings, stockpiling, or use except for listed items when approved by the Director; listed accessory structures include fences that do not require building-permit approval, with no mechanical equipment used for installation or removal.

• Utility Safety: Virginia law requires notice to the notification center / Virginia 811 before excavation or demolition where the Underground Utility Damage Prevention Act applies. For fence projects that involve excavation, including digging, drilling, augering, or other movement of earth, the excavator must submit a locate request and must review the positive-response information before work begins unless an exemption applies. A Virginia locate request is generally valid for 15 working days, and re-marking may be required before that period ends or when markings become illegible. Virginia law includes an important exemption for hand digging performed by an owner or occupant of a property. This statewide utility-notice framework is separate from local fence permitting, zoning, development approval, easement limits, right-of-way approvals, floodplain review, Chesapeake Bay Preservation Area review, Resource Protection Area review, stormwater review, wetland or shoreline approvals, HOA restrictions, and other applicable requirements.

FENCE HEIGHT AND VISIBILITY RULES

• Side And Rear Yards: In single-family residential districts, the maximum fence or wall height in a required side yard or rear yard that is not adjacent to a street is 6 feet.

• Street-Adjacent Required Yards: In a required yard adjacent to a street, a fence or wall that creates a solid screen may not exceed 2.5 feet in height, except that fences with a uniform open area of 50 percent or more may be erected to a maximum height of 4 feet.

• Height Measurement: For the single-family residential fence standards, height is measured from the average ground level adjacent to the fence or wall. The all-district fence provision also states that fence height is determined from ground level at all points on which the fence is located, and that an increase in height is allowed when spacing for drainage under the fence is needed.

• Visibility Triangle: No fence or wall may encroach into the visibility triangle. Appendix C provides the sight-triangle table by road type, and the Traffic Visibility Zone rule separately prohibits fences and other obstructions between 2.5 feet and 9 feet above property-line grade at street intersections unless an enumerated exception applies.

• Required Screening, Security, Or Safety Fences: The UDO states that the single-family residential fence standards do not prohibit fences or walls required for screening, security, or safety purposes by other sections of the UDO as determined by the Administrator.

• No Separate Residential Material-Based Height Rule: The code does not publish a separate residential maximum height based only on whether a standard fence is wood, vinyl, metal, chain link, masonry, or another ordinary fence material. The yard location, opacity, street-adjacent, visibility, overlay, drainage, stream-buffer, wetland, and site-condition rules control where they apply.

MATERIAL AND CONSTRUCTION LIMITS

• Finished Side: The finished side of any fence must face outward toward surrounding properties and rights-of-way.

• Barbed Wire And Electrified Fences: Barbed wire, electrified fences, and similar types of fences are not permitted except in conjunction with a bona fide agricultural operation.

• Open Versus Solid Street-Adjacent Fences: In required yards adjacent to a street, the UDO distinguishes solid-screen fences from open fences. Solid-screen fences are limited to 2.5 feet, while fences with a uniform open area of 50 percent or more may reach 4 feet.

• Resource Protection Area Construction: A fence in a Resource Protection Area must be designed so that surface flow is not inhibited or altered, water can flow under and through the fence unimpeded, vegetation removal is avoided, and installation disturbance is mitigated through a Minor Water Quality Impact Assessment.

• Wetland Construction: A noncommercial fence on wetlands must be constructed on pilings so that the tide can flow reasonably unobstructed and the natural contour of the wetlands is preserved.

• Drainage Spacing: The UDO allows an increase in fence height when spacing for drainage under the fence is needed. This does not allow a fence to block an open drainage channel or reduce or restrict water flow.

• Ordinary Residential Materials: The code does not specify a universal permitted-material list for standard residential fences. Material limits stated for commercial screening, industrial storage, utility facilities, solar facilities, or other nonresidential contexts are not used here as ordinary single-family residential fence rules unless the UDO expressly applies them to the residential fence situation.

PRIVATE RESTRICTIONS

Private restrictions operate independently from city fence rules. A fence that satisfies City of Suffolk requirements may still be limited by homeowners' association rules, condominium documents, subdivision covenants, deed restrictions, private easements, architectural-review covenants, conservation easements, agricultural agreements, boundary agreements, or other recorded private restrictions.

The referenced published materials do not state that City of Suffolk staff enforce private covenants or private architectural-control rules. Private restrictions may be more restrictive than public zoning, permit, or building-code requirements.

REVIEW AND ENFORCEMENT CONTEXT

Fence issues are typically reviewed during permit or approval review when required, and through complaint-based code enforcement. Examples include:

• Fence / Zoning Permit Review: The city's fence / zoning permit workflow can review fence location, height, open or solid character, zoning-district context, required-yard location, visibility-triangle compliance, street-adjacent placement, and applicable overlay or site-condition requirements.

• Building-Code Boundary: The statewide building-code baseline exempts ordinary fences of any height from building-permit application and related inspections, but that exemption does not apply when the fence is required for pedestrian safety during construction or used as a swimming-pool barrier.

• Height And Visibility: Side-yard, rear-yard, street-adjacent-yard, double-frontage, reverse-frontage, visibility-triangle, and Traffic Visibility Zone rules can be reviewed under the UDO's fence and traffic-visibility standards.

• Historic Review: In the Historic Conservation Overlay District, fences or walls that affect exterior appearance as viewed from a public right-of-way can require a Certificate of Appropriateness process, with addition or deletion of fences or walls listed as a minor action that may be approved by the Director.

• Chesapeake Bay, RPA, Wetlands, And Floodplain Review: Fence work in a Resource Protection Area, wetlands, tidal or shoreline context, or Floodplain Overlay District can trigger the applicable water-quality, wetlands, floodplain, permit, mitigation, and site-review requirements.

• Stormwater, Drainage, And Right-Of-Way Review: Broader grading, clearing, excavation, fill, drainage, driveway, right-of-way, public-works, stormwater, or land-disturbing activity connected to fence work can be reviewed under the Public Facilities Manual, Chapter 35, Chapter 74, drainage-easement rules, and right-of-way permit requirements.

• Stream Buffers And Utility Easements: The 15-foot stream-bank fence setback, open drainage-channel prohibition, major underground utility-easement limits, easement terms, and Virginia 811 utility-notice requirements can affect fence placement and installation.

• Pool Barrier Review: A fence used as a pool or spa barrier can be reviewed under pool-barrier and building-code requirements rather than as an ordinary residential yard fence.

• Rural Or Agricultural Context: Barbed wire, electrified fences, and similar fences are prohibited except with a bona fide agricultural operation. Virginia statewide livestock, lawful-fence, no-fence-law, and division-fence provisions may matter in rural, agricultural, pasture, or large-lot contexts, but they are not ordinary residential zoning height limits.

USING THIS INFORMATION

This page provides general orientation on how residential fence rules are structured and applied within City of Suffolk, based on the referenced published materials as of July 2026.

In addition to local fence rules, certain Virginia laws apply statewide. See Statewide fence laws in Virginia.

It is not legal advice and does not replace official ordinances, permits, zoning approvals, zoning certifications, development approvals, surveys, or professional guidance. Rules and interpretations may change, and application may vary based on zoning district, site conditions, easements, rights-of-way, floodplain status, stormwater requirements, Chesapeake Bay Preservation Area status, Resource Protection Area status, wetland or shoreline status, historic district status, design-review status, rural or agricultural context, livestock or division-fence context, pool-barrier use, utility safety requirements, and private restrictions such as HOA covenants, deed restrictions, private agreements, or conservation easements. Before purchasing materials or beginning construction, confirm current requirements and any site-specific limitations with the City of Suffolk Planning and Community Development Department and any applicable private agreements. If this page conflicts with official ordinances, published guidance, or direction from City of Suffolk staff, the official sources control. For legal advice or legal interpretation, consult a licensed attorney.