ForHosting KIT · Developer Utilities

Allocate Presentation Time per Slide and Section

Turn a fixed presentation duration into a practical speaking plan for every section and slide.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter the total minutes, the number of slides, and a relative weight for each section. The calculator assigns exact whole-second budgets while preserving the requested priorities and ensuring that every allocated section adds back to the total. It is useful for rehearsals, conference talks, sales pitches, lessons, webinars, and any deck where some material deserves more attention than a simple equal split would allow.

Build a realistic timing plan before rehearsing

A single average such as two minutes per slide is easy to calculate, but it rarely describes a good presentation. A title slide may need only a short welcome, while a demonstration, key chart, or recommendation may need several minutes of explanation and questions. Start by entering the complete time available, including only the portion you intend to spend presenting. Then divide the deck into meaningful sections and record how many slides belong to each one. Give every section a positive relative weight. The weights are proportions, so 1, 2, and 1 mean the middle section receives twice the time of either neighboring section; they do not represent minutes. The declared slide count must equal the sum of the section slide counts. This explicit check catches missing, duplicated, or unassigned slides before the resulting plan reaches a rehearsal. The output shows the overall average for context, but the section and slide budgets are the actionable schedule you should follow.

Understand how exact seconds are assigned

The calculator first converts the requested duration to the nearest whole second. It multiplies that total by each section's share of all weights, producing exact values that can include fractions of a second. Whole seconds are assigned first, and any remaining seconds go to the sections with the largest fractional remainders. Ties follow the original section order, making repeated calls fully deterministic. Within each section, its allotted seconds are divided evenly among its slides. If that division is not exact, earlier slides in the section receive the spare seconds. This approach guarantees that section totals add up to the presentation total and that slide totals add up to their section. It also prevents rounding drift, a common problem when independently rounded values leave a plan several seconds short or long. A formatted minutes-and-seconds value accompanies every raw seconds value, so the result is both machine-friendly and easy to use during a rehearsal.

Use weights as an editing and rehearsal tool

Treat the first result as a deliberate draft rather than an inflexible script. Rehearse with a stopwatch and note where the content naturally needs more or less room. If the central argument feels rushed, increase its weight instead of manually changing several slide times. If an introduction feels slow, reduce that section's weight and calculate again. Because weights are relative, only their proportions matter: weights of 2, 4, and 2 produce the same allocation as 1, 2, and 1. Keep audience interaction, transitions, and a closing buffer in mind. You can reserve those explicitly as named sections with their own slides, or subtract a safety margin from the total presentation duration before calculating. Very short allocations are mathematically valid and can include zero seconds for a slide when there are more slides than available seconds, but they signal that the deck needs editing. Remove slides, extend the total, or give the affected section a larger share before relying on the plan in a live setting.

Rehearse a conference talk

Give the research findings more time than the opening and references while keeping the complete talk within its assigned slot.

Plan a sales presentation

Balance discovery, product value, demonstration, pricing, and next steps according to their importance rather than their slide counts alone.

Structure a lesson or webinar

Allocate time among explanation, examples, activities, recap, and questions, then use the per-slide schedule as a rehearsal checklist.

What does it cost?

The browser calculator is free to use on this page. API requests cost $0.002 each.

Do section weights need to add up to 100?

No. Weights are relative proportions. Values of 1, 2, and 1 work the same as 25, 50, and 25.

Why must the section slide counts match the total slide count?

The equality ensures every slide belongs to exactly one timed section and prevents an incomplete allocation.

How does the calculator handle rounding?

It allocates whole seconds by largest remainder, so all section and slide values add back to the exact rounded total.

Should question time be included?

Include it as a weighted section when it belongs inside the presentation slot, or subtract it from the total duration when it is managed separately.

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.

POSThttps://api.kit.forhosting.com/biz/slide-deck-time-budget

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.

curl -X POST https://api.kit.forhosting.com/biz/slide-deck-time-budget \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"total_minutes":20,"slide_count":8,"sections":[{"name":"Opening","slides":2,"weight":1},{"name":"Core argument","slides":4,"weight":3},{"name":"Conclusion","slides":2,"weight":1}]}'
{
  "total_minutes": 20,
  "slide_count": 8,
  "sections": [
    {
      "name": "Opening",
      "slides": 2,
      "weight": 1
    },
    {
      "name": "Core argument",
      "slides": 4,
      "weight": 3
    },
    {
      "name": "Conclusion",
      "slides": 2,
      "weight": 1
    }
  ]
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "biz.slide_deck_time_budget",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →