Running Split Planner

Plan unequal route segments with individual paces and compare completed elapsed splits without hiding missing records.

Files stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

Build split plan controls

One tab-separated row per segment: a short name, the segment distance, its unit (km, m, mi, yd or ft), the planned pace per that unit written as minutes:seconds (5:30 means five minutes thirty seconds for one unit), and optionally the time you actually took for the segment as minutes:seconds. Leave the last cell empty for a segment you have not run. Up to 200 rows and 100,000 characters. The sample rows are examples; replace them with your own route.

Drop your file here

or choose one from your device

Choose a running-split-planner.json file saved by this tool to load its segments back. Import restores the editable controls and clears the file selection.

    Processed in your browser. Your inputs stay on this device.

    Showing a generated example. Generate again for a new result.

    How to use Running Split Planner

    1. Paste segment name, distance, unit and pace per that unit. The optional final cell is completed elapsed time for the whole segment.
    2. Review each segment and cumulative time. Full-route completed totals require a recorded time for every segment.
    3. Download CSV for rows, JSON to continue editing later, or PDF for a printable copy. Review exports before sharing them.

    Example: Running Split Planner

    Plan a route with three unequal segments.

    You add
    Segments: name, distance, unit, planned pace, completed time (optional): Warm-up 1 km 6:00 5:55 Middle 5 km 5:30 27:20 Finish 1.1 km 5:00 5:28
    You get
    Planned 3 segments over 7.1 km, -0:17 against the plan. Sample rows: Warm-up | 1 | km | 6:00 | 6:00 | 5:55 | 6:00 | -0:05; Middle | 5 | km | 5:30 | 27:30 | 27:20 | 33:30 | -0:10; Finish | 1.1 | km | 5:00 | 5:30 | 5:28 | 39:00 | -0:02

    Options

    Unequal distances
    A 5 km segment at 5:30/km takes 27:30. Its completed-time cell is elapsed time, not another pace.
    Rounding
    Fractional planned seconds are summed before display rounding. Displayed segment times can add to a slightly different displayed total.

    Supported inputs and limits

    Up to 200 segments. km, m, mi, yd and ft are accepted. Planned pace must be positive; missing completed times stay unknown. Processing runs in the browser without uploading entries or automatic saving. JSON projects are limited to 512 KiB. Saved files contain your supplied details. Printable reports use standard Latin fonts; unsupported characters are refused rather than omitted.

    Where your input is processed

    This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

    Pace and a completed split have different meanings

    A planned pace is time per selected distance unit. A completed split is the elapsed time for the whole segment. For a five-kilometre segment, a pace of 5:30 per kilometre means 27:30 planned time. Do not enter 5:30 as the completed segment time unless that was the full measured elapsed time.

    Questions about Running Split Planner

    Can segments have different distances?

    Yes. Each row carries its own distance and unit, and the plan adds the resulting segment times.

    What if a segment is not completed yet?

    Leave its completed-time cell empty. A missing time does not mean zero, and a full-route comparison requires completed times for all segments.

    Does the plan predict a race result?

    No. It combines the paces you choose without estimating ability, terrain effects or a suitable training pace.

    Project manager: Tony Hines · Content updated 4 October 2026 · Report a problem