ForHosting KIT · Documents & PDF

Convert PowerPoint to PDF

A deck built to be presented and a deck sent for someone to read are two different objects, and PowerPoint only gives you the first one reliably. This endpoint turns a PPTX into a PDF that opens the same way on every device, with no missing fonts, no animation half-triggered, no editable text where there shouldn't be any.

● StablePer request + per page$0.052

Run — $0.052 + $0.003/page How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

The gap between presenting and sending

A presentation file is designed around a live presenter clicking through slides with the right fonts installed and the right software open. The moment that same file is emailed as a leave-behind or uploaded to a shared drive, none of those assumptions hold — a missing font substitutes silently, an embedded video shows a blank box, and the recipient can accidentally drag a text box out of place. PDF removes every one of those variables by rendering the deck exactly as designed, once, permanently.

Who converts decks for a living

Sales teams sending a deck after a call, conference organizers compiling speaker slides into a single archive, consultants delivering a final version of a strategy presentation, training departments distributing slide decks that must look identical on every trainee's laptop. Whenever a slide deck's job shifts from being clicked through live to being read, filed or printed, this is the conversion that makes that shift work.

What the job actually does

Post the PPTX, receive a task_id straight away, and the job renders each slide as one PDF page in its original order — text, images, charts and slide backgrounds as designed, with the layout locked so nothing can be nudged out of place downstream.

Where this belongs in automation

Because it's asynchronous with billing only on success, it fits naturally after a deck-generation step: a reporting tool builds a PPTX from live data every week, this endpoint turns it into the PDF that actually gets distributed, and a webhook confirms it landed instead of a script checking back every few seconds.

A little history behind the formats

PowerPoint's presentation format moved to the XML-based PPTX in 2007 as part of the same shift that gave Word its DOCX, replacing the older binary .ppt. PDF, unrelated to either, has been Adobe's fixed-layout standard since 1993 — which is why it remains the natural resting place for a slide deck once the presenting is done and only the reading is left.

What you can do with it

Post-meeting leave-behinds

A salesperson presents from PowerPoint, then converts the same deck to PDF to email afterward so nothing shifts on the client's screen.

Conference proceedings archive

An event organizer collects speaker PPTX files and converts each to PDF to compile a single, consistent archive of the sessions.

Finalized client deliverables

A consultancy locks a strategy deck as PDF before sending it to a client, so the formatting can't be accidentally altered.

Standardized training material

A training department converts its slide decks to PDF so every trainee sees identical fonts and layout regardless of device.

FAQ

Is the PowerPoint to PDF API ready to use?

It's in deployment and will be available shortly; the endpoint and pricing here are final.

How much does it cost?

$0.052 per request plus $0.003 per page (slide), published and the same regardless of deck size.

Do embedded fonts and images survive?

Yes, slides render as designed, including fonts, images, charts and backgrounds, since the layout is fixed at conversion time.

What about animations and transitions?

PDF is a static format, so animated builds and transitions collapse to their final visible state per slide, as they would in print.

Is there a free way to try it?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

How do I get the finished PDF?

Via signed webhook when the conversion completes, or from a signed link valid for 24 hours.

Do I pay if a conversion fails?

No, failed tasks retry automatically up to three times and are never charged; you receive a clear error instead.

Can I batch-convert many decks?

Yes, each request is one file and one task_id, so converting many decks is just multiple parallel requests collected by webhook.

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

POSThttps://api.kit.forhosting.com/doc/ppt-to-pdf

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, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/doc/ppt-to-pdf \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/doc/ppt-to-pdf", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "input": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/doc/ppt-to-pdf",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "input": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/doc/ppt-to-pdf", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"input":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/doc/ppt-to-pdf", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "input": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "doc.ppt_to_pdf",
  "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

Per request$0.052

Per page$0.003

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

Limits

`max_mb`	25
`max_pages`	200

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.
`413`	`input_too_large`	The file exceeds the size limit.

Read the full KIT documentation →