Playback speed calculator
A 180-second clip played at 1.5x lasts 120 seconds, saving 60. Enter any duration and a positive speed, and the result comes back in the same unit you used, whether seconds, minutes or hours. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Duration
- 180
- Speed
- 1.5
- Adjusted duration
- 120
- Time saved
- 60
Playing a recording faster or slower changes how long it occupies the clock, not how long the file is on disk. A three-minute clip at one-and-a-half times speed finishes in two minutes; the same clip at half speed takes six. This playback speed calculator takes the original duration of a lecture, episode, audiobook chapter, or voice memo and a positive playback rate, then returns the adjusted duration as original duration divided by that rate. The unit you send is the unit you get back: seconds in, seconds out; minutes in, minutes out. Missing, non-finite, or out-of-range values fail the same way and are not billed.
How adjusted duration is computed from original duration and playback speed
Every media player that offers a speed control uses the same identity. Adjusted duration is original duration divided by playback speed. Playback speed is a positive multiplier: 1.0 is the original soundtrack, 1.25 and 1.5 are the common settings people use to finish a lecture or commute faster, and 2.0 halves the clock.
A value below 1.0 — slow motion, language study, a restored interview, or a player that stretches speech — lengthens the listen, which is why the field is not clamped to at least one. Time saved is original duration minus adjusted duration; it is positive when you speed up and negative when you slow down, so a half-speed pass of a ninety-minute seminar reports a negative ninety minutes rather than hiding the extra clock. The unit of duration is preserved on purpose.
Send seconds if your editor, caption file, or waveform viewer talks in seconds. Send minutes if a course catalog prints a forty-five-minute slot. Send hours if an audiobook card lists a twelve-hour runtime.
The arithmetic never converts between those units, so a result of one hundred twenty after an input of one hundred eighty at speed 1.5 means one hundred twenty of whatever you sent. Fractional durations are accepted because leftover seconds, chapter pads, and trailers are real; the arithmetic does not force an integer.
How the speed changes the listening time
Errors always name the canonical field so the web form can mark the right control. Zero and negative playback speed fail because a player cannot divide time by a non-positive rate — that is the contract this capability exists to enforce, and those failures are not billed. Negative duration fails for the same reason: a clip cannot last less than nothing.
A duration of zero is allowed and returns an adjusted duration of zero, which is the honest answer for an empty take. Magnitudes above the documented ceilings fail so a typo cannot blow the isolate. A familiar check is one hundred eighty seconds at speed 1.5, which yields one hundred twenty seconds adjusted and sixty seconds saved.
A one-hour file of three thousand six hundred seconds at double speed is one thousand eight hundred seconds, a thirty-minute listen. The same hour at half speed is seven thousand two hundred seconds.
What you can do with it
Fit a lecture into a class slot
Turn a forty-five-minute recording at 1.5x into thirty minutes so you know whether it still fits a single period.
Compare 1x, 1.5x, and 2x on one clip
Keep the same duration, change only speed, and see how many wall-clock minutes a faster soundtrack actually saves.
Budget caption review at a slower rate
Drop a ninety-minute interview to 0.8x and get the longer listening clock a language or accessibility pass will consume.
FAQ
How do I calculate media duration at a given playback speed?
Send two numbers: duration (original length) and speed (the playback multiplier).
What unit is duration in?
Any consistent unit you choose. Seconds in, seconds out; minutes in, minutes out. The calculator does not convert between units.
What happens if playback speed is zero or negative?
A player cannot divide time by a non-positive rate, and those failures are not billed.
How much time do I save at 1.5x speed?
A third of the original length. A 180-second clip at 1.5x lasts 120 seconds, so you save 60. The saving is reported in the same unit you entered, so minutes in means minutes out.
What happens with a speed below 1?
The listening time grows instead of shrinking. At 0.5, a clip takes twice as long, and the time saved is shown as a negative number so the extra time is never hidden.
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/audio/playback-speed \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"duration":180,"speed":1.5}'const res = await fetch("https://api.kit.forhosting.com/audio/playback-speed", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"duration": 180,
"speed": 1.5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/audio/playback-speed",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"duration": 180,
"speed": 1.5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/audio/playback-speed", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"duration":180,"speed":1.5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"duration":180,"speed":1.5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/audio/playback-speed", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"duration": 180,
"speed": 1.5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "audio.playback_speed",
"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.
Limits
max_duration | 1000000000 |
max_speed | 100 |
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
Zero or negative playback rate is rejected as invalid_input, because a player cannot divide time by a non-positive speed. Use the page in your browser at no charge, or call the API at $0.002 per successful request when a queue, a caption job, or a study plan needs the identical figure.
How adjusted duration is computed from original duration and playback speed
The response echoes the cleaned duration and speed, then returns adjusted_duration as the listening clock, time_saved as the difference, and a formula string that restates the identity so a user interface can show the rule next to the number. This endpoint does not open an audio file, does not read ID3 tags, and does not resample a waveform. It answers one question: if you play this clip at a constant speed, how long does it last.
Input contract, playback rate, response fields, and validation errors
POST a JSON body with two required fields: duration, the original length of the media in any consistent unit; and speed, the playback multiplier. Aliases original_duration, length, runtime, and time are accepted for duration; and playback_speed, playback_rate, playback, and rate for speed. Each field may arrive as a JSON number or as a numeric string; booleans, objects, empty strings, NaN, and Infinity fail with invalid_input. On success the body includes the echoed inputs, adjusted_duration as duration divided by speed, time_saved as duration minus adjusted_duration, and a formula string. Missing fields are invalid_input and are not billed. Successful API calls use the published $0.002 base price; the free browser path runs the same solve function without consuming prepaid balance.
Where a playback speed calculator earns its keep
Course designers who publish a lecture at one-and-a-half times speed need the adjusted clock so a forty-five-minute slot still fits the timetable after the soundtrack is sped up. Language students who drop a Spanish or Japanese clip to four-fifths speed need the formula with a rate below one, not a tool that silently refuses anything other than real time or double time. Audiobook clubs picking a weekly chapter can convert a listed runtime into the wall-clock they will actually spend at the club's agreed speed. Caption and subtitling desks need the same figure to budget review time: a ninety-minute interview at 1.25x is seventy-two minutes of listening, not ninety, and that difference shows up in a shift plan. Keep both inputs finite, keep speed strictly positive, pin adjusted_duration in your tests, and you get a reproducible listening clock for a lesson plan, a caption queue, a study worksheet, or an edge worker without standing up a media pipeline of your own.
Technical questions
Does this read duration from an MP3 or video file?
No. You supply the original duration yourself. The endpoint does not open containers, tags, or waveforms.
What does the playback speed calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.