Swim pace yards to meters converter
Switch a swim pace between yards and metres at the same speed: 1:15 per 100 yards becomes 1:22 per 100 metres, using the exact 0.9144 metres in a yard. Handy when you train in a yards pool and race in metres. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Pace seconds
- 75
- From
- yd
- Conversion factor
- 0.9144
- Pace s per 100m
- 82.0209973753
- Pace s per 100yd
- 75
- Pace per 100m
- 1:22
Coaches, masters swimmers, and age-group athletes constantly switch between short-course yards pools in the United States and metric short-course or long-course pools everywhere else. A pace clock that shows one minute fifteen per hundred yards is not the same workload as one minute fifteen per hundred meters, and rough mental multiples drift when you write season plans or compare meet splits. This swim pace yards to meters converter takes a positive pace in seconds per one hundred of the source unit, applies the exact international yard definition of zero point nine one four four meters, and returns the paired pace in both bases with formatted minute-second strings.
How yard and meter swim paces relate at the same speed
Swimming pace is time per fixed distance, almost always quoted per one hundred yards or per one hundred meters so athletes can read interval sets from a pace clock. If two swimmers hold the same average speed, the time to cover one hundred meters must exceed the time to cover one hundred yards because one hundred meters is longer than one hundred yards. The international yard is defined exactly as zero point nine one four four meters, so one hundred yards equal ninety-one point four four meters.
Therefore the geometric conversion at constant speed is pace in seconds per one hundred meters equals pace in seconds per one hundred yards divided by zero point nine one four four, and the inverse multiplies by that same factor. Example: seventy-five seconds per one hundred yards becomes roughly eighty-two point zero two seconds per one hundred meters, displayed as one minute twenty-two per hundred meters after ordinary second rounding for the clock string.
This capability uses only that exact length factor; it does not invent race-time turn adjustments such as the approximate one point one one multipliers sometimes used for converting full race results between short-course yards and long-course meters. Those race converters mix geometry with turn count and stroke model. Here the contract is transparent course geometry so your software can recompute both bases from a single known pace without hidden constants.
Always convert total seconds first if your UI stores minute-second strings, then call the converter with the numeric seconds field.
Where a swim pace converter earns its place in training stacks
Club coaches writing dual-course season plans need a single source of truth when a swimmer logs short-course yards intervals at home and races long-course meters abroad. College programs that travel between United States yards facilities and international metric venues can pin converted goal paces in team software instead of relying on hand calculators that mix approximate factors. Masters meet directors publishing heat sheets in both conventions can precompute equivalent pace bands for seeded entries.
Fitness apps that already store distance and finish time may still want an explicit yards-to-meters pace converter when the user edits only the pace field on a workout card without re-entering full race distance. Failed validation does not consume balance.
What you can do with it
Dual-course season planning
Convert a yards-based interval pace into the matching per-100 m goal so athletes training in SCY pools hit equivalent work when they move to metric short or long course.
Travel meet pace boards
Print paired /100yd and /100m targets on deck boards when a team races abroad and still thinks in short-course yards from daily practice.
Workout apps and pace editors
When a user edits only the pace field on a set card, recompute the other course base with the exact 0.9144 factor instead of approximate mental multiples.
FAQ
What conversion factor is used?
Pace per 100 m equals pace per 100 yd divided by 0.9144 at the same average speed; the inverse multiplies by 0.9144.
Does this apply race turn adjustments like 1.11?
No. This tool converts pure pace geometry between per-100 yd and per-100 m bases. Full race SCY↔LCM time predictors that fold in turns use different models and are out of scope.
Why is my pace per 100 metres slower than per 100 yards?
Because 100 metres is a longer distance than 100 yards. At the same average speed you need more time to cover it, so 1:15 per 100 yards turns into 1:22 per 100 metres.
How do I enter a pace like 1:15?
Convert it to total seconds first: 1:15 is 75 seconds. Then pick whether that pace is per 100 yards or per 100 metres, and both paces come back as minutes and seconds.
Can I convert from metres to yards as well?
Yes. Choose metres as the starting unit and the pace is multiplied by 0.9144 to give the yard pace. Either way you get both values, so one known pace fills in the whole plan.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/health/swim-pace-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"pace_seconds":75,"from":"yd"}'const res = await fetch("https://api.kit.forhosting.com/health/swim-pace-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"pace_seconds": 75,
"from": "yd"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/swim-pace-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"pace_seconds": 75,
"from": "yd"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/swim-pace-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"pace_seconds":75,"from":"yd"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"pace_seconds":75,"from":"yd"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/swim-pace-convert", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"pace_seconds": 75,
"from": "yd"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.swim_pace_convert",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Input contract, response fields, and validation errors
A formula string restates both identities, message summarizes the conversion direction in one line, and steps lists the arithmetic for tutoring or debug logs. When from is yards the meter pace is computed by dividing; when from is meters the yard pace is computed by multiplying. Either way both bases appear so a client that only knows one side of the pool wall still receives a complete dual readout without a second request. POST a JSON body with two required fields. pace_seconds is the swim pace as total seconds per one hundred of the source unit; it must be a finite number strictly greater than zero and not larger than one million seconds. from names the source unit and must normalize to yd for yards or m for meters; accepted aliases include yards, yard, yds, scy, meters, metres, meter, scm, and lcm among common coach spellings. Missing fields, non-numeric strings, zero, negative values, and unknown units fail with invalid_input and are not billed. On success the body echoes pace_seconds and the normalized from unit, reports conversion_factor as zero point nine one four four, and returns pace_s_per_100m and pace_s_per_100yd as numbers rounded to twelve decimal places for stable tests across runtimes. Display helpers pace_per_100m and pace_per_100yd format the same quantities as M:SS or H:MM:SS after rounding to the nearest whole second, matching how a pace clock is read.
Where a swim pace converter earns its place in training stacks
Keep pace_seconds positive, pin the rounded dual paces in tests, and you get reproducible SCY and metric hundred-split conversions for LMS plugins, edge workers, and pace-clock printers without standing up a full swimming analytics platform of your own.
Technical questions
How do I convert swim pace from yards to meters?
Send pace_seconds as total seconds per 100 yards and from as yd (or yards). The API returns pace_s_per_100m = pace_seconds / 0.9144 and a formatted pace_per_100m string, plus the echoed yard pace.
What inputs are rejected?
Missing pace_seconds or from, non-finite values, zero or negative pace, paces above one million seconds, and unknown units fail with invalid_input and are not billed.
What does the swim pace yards to meters converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.