WebP Converter API
WebP Converter transforms WebP images to classic formats like PNG and JPG, or converts other formats to WebP for better compression. Essential for handling modern web images.
The WebP Converter API provides reliable and fast access to webp converter data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use WebP Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/webpconverterCode Examples
Here are examples of how to call the WebP Converter API in different programming languages:
curl -X POST \
"https://api.apiverve.com/v1/webpconverter?outputFormat=png&quality=90&maxWidth=1920&maxHeight=1080" \
-H "X-API-Key: your_api_key_here" \
-F "image=@/path/to/image.jpg"const formData = new FormData();
formData.append('image', fileInput.files[0]);
const response = await fetch('https://api.apiverve.com/v1/webpconverter?outputFormat=png&quality=90&maxWidth=1920&maxHeight=1080', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here'
},
body: formData
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here'
}
files = {
'image': open('/path/to/image.jpg', 'rb')
}
response = requests.post('https://api.apiverve.com/v1/webpconverter', headers=headers, files=files)
data = response.json()
print(data)const fs = require('fs');
const FormData = require('form-data');
const form = new FormData();
form.append('image', fs.createReadStream('/path/to/image.jpg'));
fetch('https://api.apiverve.com/v1/webpconverter', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
...form.getHeaders()
},
body: form
})
.then(res => res.json())
.then(data => console.log(data));<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/webpconverter');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here'
]);
$postFields = [
'image' => new CURLFile('/path/to/image.jpg')
];
curl_setopt($ch, CURLOPT_POSTFIELDS, $postFields);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"bytes"
"fmt"
"io"
"mime/multipart"
"net/http"
"os"
)
func main() {
file, _ := os.Open("/path/to/image.jpg")
defer file.Close()
body := &bytes.Buffer{}
writer := multipart.NewWriter(body)
part, _ := writer.CreateFormFile("image", "image.jpg")
io.Copy(part, file)
writer.Close()
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/webpconverter", body)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", writer.FormDataContentType())
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
respBody, _ := io.ReadAll(resp.Body)
fmt.Println(string(respBody))
}require 'net/http'
require 'uri'
require 'json'
uri = URI('https://api.apiverve.com/v1/webpconverter')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Post::Multipart.new(
uri.path,
'image' => UploadIO.new(File.open('/path/to/image.jpg'), 'image/jpeg', 'image.jpg')
)
request['X-API-Key'] = 'your_api_key_here'
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.IO;
using System.Net.Http;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
using var content = new MultipartFormDataContent();
using var fileStream = File.OpenRead("/path/to/image.jpg");
content.Add(new StreamContent(fileStream), "image", "image.jpg");
var response = await client.PostAsync("https://api.apiverve.com/v1/webpconverter", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The WebP Converter API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the WebP Converter API directly in your browser with live requests and responses.
File Upload Required
multipart/form-data. Do not use Content-Type: application/json for WebP Converter. Parameters are sent as query string, not form fields.| Property | Value |
|---|---|
| Field Name | image |
| Accepted Types | .webp, .png, .jpg, .jpeg, .gif |
| Max File Size | 10MB |
curl -X POST "https://api.apiverve.com/v1/webpconverter?outputFormat=png&quality=90&maxWidth=1920&maxHeight=1080" \
-H "X-API-Key: your_api_key_here" \
-F "image=@/path/to/your/file"const formData = new FormData();
formData.append('image', fileInput.files[0]);
const response = await fetch('https://api.apiverve.com/v1/webpconverter?outputFormat=png&quality=90&maxWidth=1920&maxHeight=1080', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here'
},
body: formData
});
const data = await response.json();
console.log(data);Parameters
The following parameters are available for the WebP Converter API:
Convert WebP Image
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
image | string | required | Upload an image file to convert (supported formats: WebP, PNG, JPG, GIF) | - | - |
outputFormat | string | required | Target format Supported values: pngjpgwebpgiftiff | - | |
quality | integer | optional | Output quality (applies to jpg/webp) Range: 1 - 100 | ||
maxWidthPremium | integer | optional | Maximum width in pixels (maintains aspect ratio) Range: 1 - 10000 | - | |
maxHeightPremium | integer | optional | Maximum height in pixels (maintains aspect ratio) Range: 1 - 10000 | - |
Response
The WebP Converter API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"id": "c9d8e7f6-5432-10ba-dcfe-210987654321",
"inputFormat": "webp",
"outputFormat": "png",
"inputSize": 156789,
"outputSize": 234567,
"mimeType": "image/png",
"expires": 1707350400000,
"downloadURL": "https://storage.googleapis.com/apiverve/webpconverter/c9d8e7f6.png"
},
"code": 200
}<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<id>c9d8e7f6-5432-10ba-dcfe-210987654321</id>
<inputFormat>webp</inputFormat>
<outputFormat>png</outputFormat>
<inputSize>156789</inputSize>
<outputSize>234567</outputSize>
<mimeType>image/png</mimeType>
<expires>1707350400000</expires>
<downloadURL>https://storage.googleapis.com/apiverve/webpconverter/c9d8e7f6.png</downloadURL>
</data>
<code>200</code>
</response>
status: ok
error: null
data:
id: c9d8e7f6-5432-10ba-dcfe-210987654321
inputFormat: webp
outputFormat: png
inputSize: 156789
outputSize: 234567
mimeType: image/png
expires: 1707350400000
downloadURL: https://storage.googleapis.com/apiverve/webpconverter/c9d8e7f6.png
code: 200
| key | value |
|---|---|
| id | c9d8e7f6-5432-10ba-dcfe-210987654321 |
| inputFormat | webp |
| outputFormat | png |
| inputSize | 156789 |
| outputSize | 234567 |
| mimeType | image/png |
| expires | 1707350400000 |
| downloadURL | https://storage.googleapis.com/apiverve/webpconverter/c9d8e7f6.png |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
idPremium | string | Unique identifier for conversion request | |
inputFormat | string | Format of uploaded input image file | |
outputFormat | string | Format of converted output image file | |
inputSizePremium | number | Size of input image in bytes | |
outputSizePremium | number | Size of converted output image bytes | |
mimeType | string | MIME type of converted output image | |
expires | number | Unix timestamp when converted image expires | |
downloadURL | string | URL to download converted image file |
Headers
Required and optional headers for WebP Converter API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
CORS Support
The WebP Converter API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call WebP Converter directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call WebP Converter directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
WebP Converter API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all WebP Converter users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each WebP Converter response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, WebP Converter returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for WebP Converter:
- Monitor the rate limit headers to track your WebP Converter usage (Free plan only)
- Cache webp converter responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle WebP Converter performance
Note: WebP Converter rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using WebP Converter on Free tier.
Error Codes
The WebP Converter API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate WebP Converter with SDKs
Get started quickly with official WebP Converter SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate WebP Converter with No-Code API Tools
Connect the WebP Converter API to your favorite automation platform without writing code. Build workflows that leverage webp converter data across thousands of apps.





All platforms use your same API key to access WebP Converter. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for WebP Converter?
How many credits does WebP Converter cost?
Each successful WebP Converter API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful webp converter lookups.
Can I use WebP Converter in production?
The free plan is for testing and development only. For production use of WebP Converter, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use WebP Converter from a browser?
What happens if I exceed my WebP Converter credit limit?
When you reach your monthly credit limit, WebP Converter API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.



