Skip to content

Platform & API

One engine. Eleven brands. Your API.

Everything we ship runs on one platform we write and operate ourselves: the design canvas, the conversion engine, AI we host ourselves, accounts and payments, apps for every screen and a public API.

The engine

Files in, anything out, around the clock.

Documents, images, video, audio, e-books, archives and CAD files go in. The right format, a smaller file, editable text or an AI-enhanced image comes out. Our engine handles more than a million processing jobs on a busy day.

Every brand uses it, and so does every API customer. Improve it once and everyone gets faster.

  • Websites, iOS and Android apps, browser extensions and the API share one backend
  • Shared accounts and payments, with sign-in through Google, Apple or Microsoft
  • Apps for Zapier, Make and the Google Workspace Marketplace

In-house tech

What the platform does.

All of it powers our brand websites and apps, and much of it is open to developers through the API.

  • Design

    The Workspace: a canvas in the browser for posts, flyers, résumés and presentations, with text, images, shapes and AI on the page.

    Workspace
  • Editing

    Merge, split, sign and redact PDFs, crop and resize images, cut videos, trim and normalize audio.

    PDF2Go
  • Self-hosted AI

    Background removal, upscaling, colorizing, image generation, speech to text and PDF summaries, on models we host ourselves.

    Img2Go
  • Conversion

    Documents, images, video, audio, e-books, archives and CAD, from one format to another.

    Online-Convert
  • Compression

    Smaller PDFs, images and videos, by quality or target size, plus ZIP and other archives.

    Compress2Go
  • Text recognition

    Text from scans, photos and PDFs, as editable Office files or searchable PDFs.

    OCR2Edit
  • Metadata

    Read, edit and remove the hidden metadata of images, documents, audio and video.

    Metadata2Go
  • Website capture

    Any public web page, saved as a PDF or an image straight from its URL.

    API2Convert

api2convert API

Our engine, one request away.

Create a job with an input and a target format. The engine does the rest and, if you ask it to, calls your webhook when the result is ready.
  • Official open-source SDKs for PHP, Python, Node.js, Java, .NET, Go, Ruby and Rust, plus an open-source command-line tool
  • Webhooks when a job finishes or on every status change, retried if your endpoint is briefly down
  • Inputs from uploads, URLs, Amazon S3, Azure or Google Cloud Storage; results as download links or delivered to S3, Google Cloud Storage, Azure, SFTP or Google Drive
  • You stay in control: withdraw a result so its link dies immediately, remove source files as soon as a job finishes, protect downloads with a password
# Create a job: convert a DOCX file from a URL to PDF
curl -X POST "https://api.api2convert.com/v2/jobs" \
  -H "x-api2convert-api-key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "input": [{
      "type": "remote",
      "source": "https://example-files.online-convert.com/document/docx/example.docx"
    }],
    "conversion": [{
      "category": "document",
      "target": "pdf"
    }],
    "process": true
  }'

# Then poll GET /v2/jobs/{id} until the status is "completed",
# or add "callback": "<your-webhook-url>" to the job.

How a job runs

From file to result, fully automated.

  1. Send a file or a link

    Upload a file, pass a URL or point to cloud storage. Each job gets its own ID and its own access token.

  2. The engine takes over

    The job is queued and handed to our processing servers. AI tasks go to models we host ourselves in the EU.

  3. Result and webhook

    The result waits as a download link or lands straight in your cloud storage, and your webhook gets the call.

  4. You stay in control

    Your files are used only for your task. Withdraw a result through the API and its link stops working immediately.

Infrastructure

Infrastructure we run ourselves.

The platform runs on dedicated servers we operate ourselves, not on a public cloud.

  • Dedicated servers

    Websites, API and conversion engine run on dedicated servers in the EU that we operate ourselves.

  • Our own AI

    Unless an app says otherwise, AI runs in the EU on our own infrastructure, with models we host ourselves.

  • Global delivery

    Websites and API are delivered through a global content delivery network with built-in DDoS protection.

  • Redundant

    Our main websites and the API run on redundant servers in separate data centers.

  • Encrypted

    TLS for every connection, full-disk encryption on our servers.

  • Backed up

    Backups are encrypted before they leave our servers and are stored off-site.

Planning an integration?

Tell us about your files, volumes and requirements. We’ll help you find the right setup, from a first test to an enterprise agreement.