Skip to content
API REFERENCEv2

CSV to JPEG API

Prepare a JPEG rendering of the data table from a delimited export with the TableConvert conversion API. CSV has no original page style or cell types to preserve; inspect the newly generated table’s readability.

REST APIv2 · Direct outputCSV → JPEG table image5 credits per successful conversion

Try this conversion

Inspect a real sample, preview locally, or send a live request with your own key.

Verified sample
POSThttps://api.tableconvert.com/v2/convert/csv-to-jpeg

JPEG table image response

CSV to JPEG API · Verified samplecsv-to-jpeg.jpg
Content-Type
image/jpeg
Size
6,964 bytes
Download sample response

Binary previews show the verified sample file. Send a live API request to generate a new file from your input.

A successful live request uses 5 credits.

Your key is sent only to the conversion API and is never saved by this page.

Things to check before integrating

Before you integrate

Check the separator, quoted line breaks and identifier columns before generating the destination.

Before you integrate

Source page styling is not captured, and raster text is not a substitute for editable data.

Before you integrate

The public image endpoint has no theme option: unregistered theme fields are discarded, and the API uses its fixed table styling.

Code examples

These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.

CSV to JPEG API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/csv-to-jpeg' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data="item","quantity","status"
"Notebook","12","Available"
"Marker","8","Reserved"' \
  --output 'csv-to-jpeg.jpg'

Requires cURL. Download the sample input first when this example uploads a file.

Authentication

Send Authorization: Bearer YOUR_API_KEY. Let the HTTP client set the multipart boundary; do not set Content-Type manually.

Keep production API keys in server-side environment variables.

Request parameters

Delimited text is parsed into a rectangular table before the requested output is generated. A header row and consistent separators make field mapping explicit.

ParameterTypeDefaultDescription
datastring—Inline CSV table content. Choose one of data, file or url.
filebinary—Upload a csv file using multipart/form-data.
urlstring—A supported publicly accessible HTTP or HTTPS file URL.

Send one source: data, file, or url. The examples below use the source mode appropriate for this format.

Output options

Render the normalized data table as a JPEG image. This produces a new table image rather than a screenshot of the source document or webpage.

This output format does not expose additional options.

Conversion rules

CaseBehavior
Mapping rule 1The CSV header becomes the table’s first row; subsequent delimited records become data rows.
Mapping rule 2Extracted cell values are laid out into a new raster table image.
Mapping rule 3CSV has no original page style or cell types to preserve; inspect the newly generated table’s readability.

How the input is read

  • Use the first row for column names when the destination creates named records or schema fields.
  • Quoted separators, escaped quotes and quoted line breaks are parsed as cell content; inconsistent rows are padded to the table width.
  • Normalize mixed separators before conversion; automatic delimiter detection is a heuristic.
  • CSV cells become text; a numeric-looking identifier and an actual numeric type are not interchangeable.

How the output is written

  • Save the binary response as a JPEG file; do not parse it as text.
  • Image output is a presentation artifact and no longer exposes editable cells.
  • Check long values, column count and character rendering in the downloaded image.
  • The public image endpoint has no theme option: unregistered theme fields are discarded, and the API uses its fixed table styling.

When to use this API

This conversion in practice

Use a delimited export as the starting dataset for a visual table shared in a report. Check the separator, quoted line breaks and identifier columns before generating the destination.

JPEG table image

Share a fixed visual table in a report, slide or message.

Responses and errors

HTTP statusDescription
200image/jpeg
400Invalid input or conversion parameters.
402Insufficient credits for this request.
403Missing or invalid API key.
413The input exceeds the configured request limit.
415Unsupported input media type.
429Rate limit exceeded.
500The conversion could not be completed.
503The renderer is unavailable or the request timed out.

Check the response before retrying. A new HTTP request is a new conversion and may use credits again.

Limits, billing and versions

Local previews accept up to 200 KB. The current API implementation allows one uploaded file up to 50 MiB, limits each multipart text field to 1 MiB, and gives v2 conversion tasks a 30-second deadline. Deployment limits may be stricter. Read the returned error before retrying; some parser or renderer failures return HTTP 500.

Live calls follow the API credit policy. Failed conversions are refunded; a completed conversion is not undone if the download connection later fails.

View API pricing and credits

Using API v1?

This page documents v2, which returns the output directly. API v1 wraps the result in a JSON envelope. Check the overview before changing an existing integration.

API overview

References and format specifications

Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.