Buy credits
Choose any existing credit pack. Your account receives API access automatically after payment.
Add screenshots, PNG/JPG/WebP images, and PDFs to your product or workflow, then convert them asynchronously into editable PowerPoint. Text, shapes, and tables are rebuilt as native PPT elements where possible instead of simply placing the source image on a slide.
Buy any credit pack to activate API access automatically. No sales call required. The API and web app share credits.
curl -X POST https://image2ppt.com/api/v1/jobs \
-H "Authorization: Bearer i2p_live_xxx" \
-F "files=@slide.png" \
-F "files=@report.pdf" \
-F "locale=en" \
-F "aspectRatio=16:9"
Use your current account and credits — no separate contract or manual approval.
Choose any existing credit pack. Your account receives API access automatically after payment.
Create a key in the developer console. The full secret is shown once, so store it on your server.
Upload images or a PDF, poll the job status, and download one editable PPTX when it finishes.
Text boxes, regular shapes, and tables are rebuilt as native PowerPoint elements where possible; complex visuals may remain image elements.
Supports PNG, JPEG, WebP, GIF, and PDF, uploaded directly or fetched from your URLs. Pick just the PDF pages you need; files in one request are merged into one deck in order.
Python and Node.js/TypeScript clients wrap submission, polling, download, rate-limit backoff, and error mapping.
The API and web app use the same balance. One successful page costs one credit; failed pages are refunded automatically.
Each file can be up to 35MB, with up to 90MB of total file content per request, and each job can contain up to 50 pages (selected pages are what count). One account can have 10 active jobs and submit up to 60 pages per minute. A webhook tells your service when a job finishes, an idempotency key makes retries safe from double charges, and the job list shows per-job usage by date for easy reconciliation. API-generated PPTX files are retained for 7 days.
Use the existing three credit packs; larger packs cost less per page, and there is no monthly minimum. Credits are reserved on submission and settled only for pages successfully produced.
Yes. Paid accounts can create API keys in the developer console and use the public /api/v1 endpoints to submit, inspect, and download jobs.
No. Buying any existing credit pack activates API access automatically, and the API shares the web app balance with no monthly minimum.
Yes. A job can include multiple images and PDFs, or up to 50 file URLs, with up to 50 pages total, merged into one PPTX in order; for long PDFs you can select just the pages you need.
No. Keep the key on your server or in a secure job environment; never embed it in a website, mobile app bundle, or public repository.
Read the endpoint and error reference, then open the console to create a key. Both Python and Node.js SDKs include runnable examples.