Wood Picket Fence Material Calculator

Estimate posts, rails, and pickets for an open straight fence run.

Inputs

Preset: 48 ft picket fence

A straight run with assumed 8 ft post spans, two rails per span, 5.5 in pickets and 0.5 in gaps. Gates, corners and end clearances need separate layout adjustments.

Post count - Length (ft), Post spacing (ft)
Enter length in ft.
Enter post spacing in ft.
Formula, inputs and conditions

Formula: ceil(Length/Post spacing)+1

Decimal results are displayed to two places when needed.

Inputs
Net run length, post spacing from the plan, picket width and gap, and rails per bay.
Outputs
Post, rail, and picket counts.
Conditions and scope
Limited to one open straight run. Gates, corners, and shared posts need a segment-by-segment plan. The preset spacing illustrates the count; confirm spacing and structural dimensions from the intended fence system. Results are planning estimates, not engineering, permit, code or contractor-price decisions.

Count the spans in a straight fence run

A straight open run has one more post than the number of spans. Rails are counted per span, while pickets are estimated from their repeating width-plus-gap module. Gates and corners can change the layout and need separate treatment.

Measure and calculate

  1. Measure one straight uninterrupted run and choose its intended maximum post span.
  2. Enter rails per span when using rail mode.
  3. Use actual picket face width and clear gap for the picket count.
Calculation method

Posts = ceiling(run length ÷ intended span) + 1.

A worked example

Inputs
A 48 ft straight run is divided into 8 ft spans.
Calculation
48 ÷ 8 = 6 spans; 6 + 1 = 7 posts.
Result
7 post

The initial estimate is 7 posts. With two rails per span, the same run uses 12 rails. This simple count does not place gates or determine safe post spacing.

Read the result

Output interpretation and next steps
Output or checkWhat it means for your project
Posts and railsFor one open run, posts equal whole spans plus one; rail count uses whole spans times rails per span. Shared corners and gates need a separate layout.
PicketsPicket mode uses actual face width and clear gap. Check the end conditions rather than assuming every run finishes with the same gap.

Common questions

Why is there an extra post?

Each open straight run needs a post at both ends; adjacent spans share their intermediate posts.

Can I add counts for several adjoining runs?

Check shared corners before adding them. Counting each run independently can count the same corner post twice.