Home and construction

Fence Calculator

Work out the posts, panels or sections, rails and pickets for a fence from the length of each side, the post spacing and any gates.

Rules last checked 10 November 2026Every step shown

Your numbers are saved in this browser.

One number per straight run, in metres (or feet). A corner goes between each.

Often the width of one fence panel, or 2 to 3 m (6 to 8 ft) for wire and rail fences.

In cm (or inches). Leave at 0 for panels, wire or rails only.

In cm (or inches).

In metres (or feet). Gates take away from the pickets but still need posts.

Posts

26

Sections or panels
25
Fence length
55 m
Rails or wire runs
75 (165 m in all)

55 m of fence in 3 sides needs 26 posts and 25 sections, with 75 rails.

How it's worked out

  1. Side 120 m ÷ 2.4 m, rounded up9 sections of 2.22 m
  2. Side 215 m ÷ 2.4 m, rounded up7 sections of 2.14 m
  3. Side 320 m ÷ 2.4 m, rounded up9 sections of 2.22 m
  4. Posts25 sections + 126
  • Corner and gate posts take the most strain: use stronger posts and set them deeper. Add a few spares for breakages.

How it is worked out

Each side is split into equal sections no longer than your post spacing. Posts = sections + 1 for an open fence, or sections for a closed one, plus one for each gate. Rails = sections × rails per section.

Questions people ask

How many posts for a 55 m fence in three sides at 2.4 m spacing?

26 posts and 25 sections, with sides of 20 m, 15 m and 20 m and the ends not joined.

Why do I need one more post than sections?

Each section needs a post at both ends, so a straight run of 10 sections needs 11 posts. A fence that goes all the way round shares its first and last post.

How are pickets counted?

The fence length, minus any gates, divided by the picket width plus the gap, rounded up.

Do corners need extra posts?

No extra posts are needed, as each corner already has one, but use stronger posts there and at gates.

About this calculator

Formula and rules last checked 10 November 2026Written and tested by the CalculatorDex teamReport a problem