How to Automate WebP to PNG Conversion in Clay Pipelines

Over 90% of lead list designers face format compatibility errors in email client delivery when sending campaigns containing WebP image assets, despite Google documentation showing WebP files are up to 30% smaller than PNGs. This delivery bottleneck is where programmatic asset conversion in outbound pipelines becomes critical. While WebP works well for browser rendering, legacy desktop clients like Microsoft Outlook often display broken image links for WebP attachments.

WebP to PNG conversion in Clay refers to programmatically transforming web-optimized image assets into transparent PNG format using custom HTTP enrichment steps. When scrape engines pull data from corporate profiles, they often grab modern WebP formats to save bandwidth. However, outbound systems need reliable formats. If your email campaign includes personalized screenshots or logo previews, sending a WebP image increases the risk of delivery failures.

Clay provides a spreadsheet-like database where outreach engineers enrich lead lists with email addresses, firmographics, and social profiles. However, Clay lacks a native tool to transform image file formats in bulk. Competitors only cover manual browser uploaders and lack developer integration steps for spreadsheet-like bulk conversion. Outbound engineers need an automated path that handles thousands of conversions directly within a table. By using Clay's HTTP API enrichment step, teams can connect external image conversion endpoints to convert WebP files to PNGs automatically.

To build an automated image conversion step, you must choose an external service with an API that connects to Clay. Two primary options are CloudConvert and Cloudinary. Each has distinct architectural differences.

Cloudinary is designed for real-time media management and dynamic web delivery. It converts images on-the-fly when a browser requests them. For example, changing a file extension in a Cloudinary image URL from .webp to .png automatically converts the asset. This is useful for dynamic web applications, but less practical for outbound spreadsheets where you need to verify, process, and attach static files.

CloudConvert uses a job-based system designed for batch processing. You write a request that imports a file, executes a conversion task, and exports the final file. This fits Clay's row-based execution model. To convert a WebP to a PNG, you send a JSON payload defining three tasks: importing the source WebP URL, executing the format conversion, and exporting the new PNG.

A typical CloudConvert job payload looks like this:

{
  "tasks": {
    "import-image": {
      "operation": "import/url",
      "url": "https://example.com/source-image.webp"
    },
    "convert-image": {
      "operation": "convert",
      "input": "import-image",
      "output_format": "png"
    },
    "export-image": {
      "operation": "export/url",
      "input": "convert-image"
    }
  }
}

CloudConvert processes this job and returns a temporary URL containing the converted PNG. This URL is then mapped back into your Clay table. You can research further details in the official CloudConvert API Documentation to configure advanced parameters.

Clay's official HTTP API documentation confirms support for connecting custom headers and payloads to execute programmatic webhook and API queries. Using this feature, you can trigger the CloudConvert job directly for each row in your table.

To set up the enrichment step, follow these instructions:

First, open your Clay table and click the Add Enrichment button. Search for and select the HTTP API tool.

Second, select the request method and endpoint. Set the method to POST. Enter the CloudConvert Job API URL: https://api.cloudconvert.com/v2/jobs.

Third, configure the headers for authentication. CloudConvert requires a Bearer token. Create a new account under Clay's HTTP API (Headers) settings. Save your credential with the key Authorization and the value Bearer YOUR_CLOUDCONVERT_API_KEY. This keeps your API key secure and reusable across other columns. You can find detailed requirements in the Clay HTTP API Enrichment Documentation.

Fourth, write the request body. You must pass the JSON configuration for the conversion job. In the body editor, paste the task payload structure. To make the import task dynamic, replace the static URL with your table's column variable. Type / in the URL field and select the column containing your raw WebP image URL.

The dynamic payload in Clay will look like this:

{
  "tasks": {
    "import-webp": {
      "operation": "import/url",
      "url": "/WebP Image URL"
    },
    "convert-to-png": {
      "operation": "convert",
      "input": "import-webp",
      "output_format": "png"
    },
    "export-png": {
      "operation": "export/url",
      "input": "convert-to-png"
    }
  }
}

Fifth, run a test on a single row. Once the test finishes, examine the API response. Locate the export-png task in the JSON output, and find the result.files[0].url key. Click this key and choose to map it to a new column in your table. This column will now automatically populate with the converted PNG URL for every row you run.

The output URL returned by CloudConvert is temporary. CloudConvert automatically deletes files from their servers after 24 hours to protect user privacy. If you attempt to send an email campaign using these temporary links after that window, the images will fail to load, resulting in broken links for your recipients. You must copy and store the converted PNG files in a permanent workspace.

Outbound teams often consider three storage alternatives:

First, downloading files to local storage is a common fallback, but it requires manual effort and breaks automated pipelines.

Second, Amazon S3 provides permanent storage, but configuring bucket permissions, IAM policies, and credential rotation adds technical complexity that non-technical team members cannot manage.

Third, Google Drive offers simple storage, but its API limits often slow down bulk processing, and file indexing is not real-time.

Fastio provides a premium alternative. A Fastio workspace serves as a shared workspace where agents and humans collaborate on the same files. Organ-owned Fastio Workspaces keep all assets organized, with version history kept for every file.

Unlike standard storage providers, Fastio has no permanent free plan and no free agent tier. A Starter plan is priced at $29 monthly, a Business plan is $99 monthly, and a Growth plan is $299 monthly. New organizations start with a 14-day free trial, which requires a credit card. You can view all features on the Fastio Pricing page.

You can automate the transfer from Clay to Fastio using the Fastio Cloud Import tool. Instead of performing local disk reads and writes, the Cloud Import API imports files directly from a public URL. You write a script or use an automation tool to take the PNG URL from Clay and call the Fastio import endpoint, saving the file directly to your workspace.

Once files are imported, you can use Metadata Views to turn your document folder into a live, queryable database. By visiting the Metadata Views product page, users can describe the fields they want extracted in plain English. Fastio's AI automatically suggestions schemas and extracts data like file dimensions, dominant colors, or text contents into a spreadsheet view. This allows your team to query and sort assets (for example, finding all PNGs with transparent backgrounds or specific resolutions) without running manual checks. This structured extraction layer operates separately from general workspace search, providing clean database tables from your files.

Store your converted WebP to PNG assets in Fastio

Set up a shared, intelligent workspace with automatic file indexing, version history, and Metadata Views for your WebP to PNG conversion assets. Start your 14-day free trial.

Start 14-Day Trial

When running image conversion pipelines at scale, you must plan for API constraints and edge cases. Processing leads simultaneously can quickly hit rate limits or exhaust your API credits.

To optimize your pipeline, implement these steps:

First, configure Clay's conditional run logic. Do not execute the HTTP API enrichment step if the image URL column is empty or does not contain a WebP extension. This prevents wasted credits on broken inputs.

Second, handle API rate limits. CloudConvert limits concurrent jobs based on your plan level. When writing your connection script, implement a retry mechanism with exponential backoff to handle HTTP rate limiting responses.

Third, set up event-driven webhooks. Instead of polling the CloudConvert API to check if a job is complete, configure a webhook URL in CloudConvert. When the conversion task finishes, CloudConvert sends a POST request to your webhook, which can trigger the import to your Fastio workspace automatically.

Finally, monitor your credit usage. Fastio meters AI work with credits, so ingesting and processing images draws from your included allowance, while storage and seats come with the plan. Run a small batch first and read the actual draw off the usage dashboard, then size the full job against it so the pipeline never pauses on credit exhaustion. If it does run over, overage is billed at $10 per 100,000 credits.