How to Convert HEIC to PNG for Clay GTM Asset Pipelines

US searchers look up "heic to png" about 49,500 times per month, with keyword difficulty around 9 and CPC near $0.05, according to DataForSEO keyword metrics updated in July 2026. That volume looks like a simple format fix. For Clay go-to-market desks, it is usually a pipeline gap: iPhone field photos, event shots, product stickers, and founder headshots arrive as HEIC, then break when design tools, transparent overlays, or multi-channel campaign packages expect PNG.

HEIC to PNG converts Apple's High Efficiency Image format into PNG so GTM teams can use iPhone-captured assets in design tools, transparent overlays, and Clay-linked campaign packages. Apple Support documents that HEIF (the container behind many HEIC photos) and HEVC offer better compression than JPEG and H.264, so devices and iCloud Photos use less storage while keeping the same visual quality. On supported iPhones and iPads, High Efficiency capture is the default unless Camera Formats is set to Most Compatible, which writes new photos as JPEG.

That storage win becomes friction the moment creative leaves the Apple stack. Windows machines, many email builders, browser-based design tools, and partner portals still mishandle HEIC. Canva's HEIC to PNG converter product page notes that HEIC is strong for storage-friendly quality on Apple devices, but is not as universally compatible as PNG across software systems. CloudConvert's HEIC to PNG tool describes HEIC as the standard for storing images on Apple mobile devices starting with iOS 11, and PNG as a lossless raster format commonly used for website graphics.

Clay sits next to that creative handoff for many GTM teams. Clay is not a native HEIC converter. Clay University's Claygent Builder docs show agents built for research, scoring, and copywriting, with document uploads for tone guides, messaging docs, PDFs, and CSVs. Clay's export lesson treats export as the bridge from Clay tables into CRMs, sequencers, Sheets, and other operational tools. When field or iPhone assets enter those creative and export workflows, normalize HEIC first so PNG (or JPG) files are ready before rows leave Clay.

Most free converters treat PNG and JPG as interchangeable download buttons. They are not. Pick the format before you convert, or you will re-export the same phone dump twice.

Choose PNG when you need any of the following:

• Transparency for logos, stickers, product cutouts, or overlays on landing pages and ads
• Lossless edges for screenshots, UI captures, charts, or text-heavy slide stills
• Further design edits in tools that prefer a clean alpha channel or lossless source
• Brand marks that must sit on colored backgrounds without a white box
• Creative packages where designers will composite the mobile photo into a template

Choose JPG when you need any of the following:

• Full-bleed photos without transparency (event floors, office tours, team group shots)
• Smaller files for email sequences, CRM avatar fields, or paid social size caps
• High-volume photo libraries where storage and bandwidth cost more than pixel-perfect edges
• Destinations that reject PNG or silently re-compress large transparent files

Quick rule for Clay ops

If the asset will be composited (logo on a hero, sticker on a one-pager, cutout for a personalized page), convert HEIC to PNG. If the asset is a complete photographic frame that only needs broad compatibility, convert HEIC to JPG instead. Many teams keep both: a PNG master for design, and a JPG delivery copy for outbound.

Email sequences rarely need HEIC. Most ESP creative builders and HTML email clients expect JPG, PNG, or GIF. HEIC attachments often fail to preview for Windows recipients, or they never render inside the template at all. Convert before the image enters the sequence builder. Prefer JPG for photographic banners to keep message weight down. Prefer PNG when the creative depends on transparency or sharp logo edges.

What converters usually skip

Converter landing pages stop at "upload, convert, download." They rarely document when PNG is required versus JPG, how to name files for multi-channel reuse, or how ops should store mobile-captured assets so Clay, design, and SDR tools share one library. That storage step is the real GTM work.

Use this sequence whether you convert one founder cutout or a folder of event stickers before a Clay campaign load.

1. Decide PNG or JPG. Apply the rule above per asset type. Do not batch everything to PNG by default. Transparent masters and full-bleed photos have different destinations.
2. Convert HEIC to the chosen format. On a Mac, Apple Support documents export from Photos or Preview: open the HEIF image, choose File > Export, and select PNG (or JPEG) before saving. For browser work, Canva's free HEIC to PNG converter supports upload, optional edit, and PNG download. CloudConvert supports HEIC to PNG with controls for resolution, quality, and file size. Desktop batch tools and conversion APIs fit larger event dumps.
3. Run a quality checklist, then store the files in a shared library. Confirm orientation, transparency (for PNG), file size, and naming before anyone pastes a link into Clay. Local Downloads folders and personal Drive dumps work for a solo test. Team pipelines need a shared library with permissions.
4. Reference durable URLs in Clay and campaign packages. Keep Clay rows light: store png_url or jpg_url, asset type, account key, and conversion status. When lists leave Clay, export clean views that include those URLs so sequencers, CRMs, and design folders all point at the same files.

Desktop and phone capture tips

On iPhone, Camera > Formats > Most Compatible writes new photos as JPEG and reduces future HEIC intake. Existing High Efficiency libraries still need conversion. Apple notes that when you share HEIF media by AirDrop, Messages, or email and the receiver does not support newer formats, the media may automatically arrive as something more compatible such as JPEG. That casual handoff does not give you a controlled PNG with transparency for design work.

Online HEIC converter PNG options

Browser tools are fine for ad hoc work. Canva positions HEIC to PNG conversion as a path to share across operating systems, edit in the design surface, and download as PNG. CloudConvert documents HEIC as the Apple mobile standard and PNG as a lossless web-oriented graphic format. Neither download replaces a team asset library. Files that live only on one laptop will not survive the next multi-channel play.

Store HEIC to PNG outputs for Clay campaigns

After you convert HEIC to PNG for Clay GTM packages, keep the files in an org-owned Fast.io workspace with version history, Intelligence Mode search, and durable share links your tables can reference. Start with a 14-day free trial.

Start 14-Day Trial

Clay GTM teams usually treat people and company data as first-class tables. Mobile-captured creative should get the same discipline: a small asset table, stable joins, and URLs that outlive the original AirDrop thread.

Table design for creative rows

Build a dedicated Clay table for assets, separate from enrichment waterfalls:

• asset_id: stable internal ID
• source_heic_url or intake note: where the original phone file landed
• account_name / CRM ID: join keys back to people and company tables
• asset_type: headshot, logo_overlay, product_cutout, event, screenshot, other
• output_format: png or jpg
• png_url / jpg_url: durable link after conversion and storage
• needs_transparency: yes or no (drives the PNG rule)
• conversion_status: pending, success, failed
• approved_for_outbound: human review flag
• notes: crop, rights, or usage limits

Keep enrichment and asset conversion in related tables when possible. Mixing phone photos into a wide enrichment waterfall makes failures hard to debug.

Claygent context and creative packages

Claygent Builder is Clay's hub for building, testing, and deploying Claygents for judgment-based GTM work such as account research, lead scoring, outbound copywriting, and persona classification. Official docs describe document uploads so agents can attach tone guides, messaging docs, PDFs, or CSVs. That context layer works better when campaign creative is already normalized: PNG overlays and JPG photos live in a shared library, and Clay rows hold URLs the team can also hand to designers.

Do not invent a built-in Clay HEIC converter. Treat conversion as an external step (Preview export, Canva, CloudConvert, or a conversion API). Clay orchestrates the GTM data and export path; pixels live in storage.

Export handoff

Clay University's export lesson frames export as the final FETE step: the bridge from Clay workflows into CRMs, email sequencers, Google Sheets, and other action systems. CSV export is the universal transfer path. Dedicated export views should hide intermediate columns and keep only values that matter, including asset URLs. Real-time integrations fit when data must stay synchronized; static CSV exports fit one-time campaign packages and backups.

For multi-channel plays, a practical package looks like:

1. Clay export view with account, contact, offer fields, and png_url / jpg_url
2. Shared folder of approved PNG masters and JPG deliveries
3. Design kit (Canva, Figma, or agency brief) that pulls from the same URLs
4. Sequencer or CRM fields that reference the same image links

If the PNG only exists in one person's Downloads folder, the package breaks the first time an SDR, designer, or contractor needs the file.

Conversion without shared storage recreates the HEIC problem in a new container. Someone still owns a ZIP, and Clay still points at a dead path.

Local disk works for a designer reviewing ten cutouts. It fails when marketing ops, an agency, and an enrichment agent all need the same transparent logo next week.

Google Drive, Dropbox, or OneDrive are the usual next step. Shared drives solve basic collaboration. Search is often filename-first, permissions drift across freelancers, and there is little structure for agent access or immutable activity history.

Object storage such as Amazon S3 is durable and cheap at volume. Engineering teams often put public marketing assets behind a CDN. The tradeoff is operational overhead: bucket policies, cache invalidation, and no native review surface for non-engineers.

Fast.io fits when the library is part of an agentic GTM workspace rather than only a static CDN folder. Create an org-owned workspace such as gtm-creative-png-2026, upload converted PNGs and JPGs, and organize folders by account or campaign. Enable Intelligence Mode so files are indexed for semantic search and citation-backed chat. Ops can ask for "Acme transparent logo from the June field shoot" instead of guessing date folder names.

For structured catalogs, use Metadata Views to extract fields such as account name, asset type, transparency flag, shoot date, brand color tags, and approved-for-outbound status into a sortable grid. Metadata Views are the structured extraction layer. Intelligence Mode remains the search and summarization layer. Agents can create Views, trigger extraction, and query results through Fast.io's consolidated MCP tools over Streamable HTTP at /mcp or legacy SSE at /sse. See storage for agents for the current MCP skill surface.

Permissions stay granular at org, workspace, folder, and file levels. Per-file version history matters when a designer replaces a crop or a conversion rerun fixes a broken alpha channel. The append-only audit log records who uploaded or replaced assets. Branded shares (Send, Receive, or Exchange) let agencies drop HEIC intakes or pick up approved PNG packs without full workspace admin. Receive shares help after trade shows when reps upload phone photos without mailing multi-megabyte attachments.

Agents and humans can share the same workspace. An agent can upload converted PNGs through the API or MCP, leave Collaborative Notes on review status, and transfer organization ownership to a human ops lead when the workspace is ready for billing control. Creating an account is free, but real work requires an organization on a paid subscription. Every org starts with a 14-day free trial that requires a credit card. Plans include Starter at $29/mo, Business at $99/mo, and Growth at $299/mo. Details live on pricing and storage for agents.

Once PNGs live in shared storage, Clay should reference URLs, not binary cells. Binary cells are hard to audit, hard to reuse across tables, and painful to re-fetch after export.

Recommended handoff pattern

1. Decide PNG versus JPG using the decision rule.
2. Convert HEIC with Preview, Canva, CloudConvert, a batch tool, or a conversion API.
3. Upload approved files to Fast.io (or S3/Drive if that is your standard).
4. Write the durable share or file URL into Clay png_url or jpg_url.
5. Join that URL onto people and company tables by account or CRM ID.
6. Export a clean Clay view that includes asset URLs for sequencers, CRMs, and design kits.

If upload is automated, a worker can watch conversion success, push files into Fast.io, then post the final URL back into Clay. Fast.io webhooks help on the storage side: when a new file lands or a version changes, notify your worker so Clay rows update without polling.

Human review loop

Not every converted image should go live. Transparent PNGs need a second look for jagged edges, leftover backgrounds, and color profile shifts. In Fast.io, tasks and approvals can sit beside the files: assign a designer to check alpha channels, require marketing sign-off for customer logos, and keep comments anchored to the image. When the team approves a version, update Clay once.

Failure modes to plan for

• Wrong format choice: JPG cannot carry transparency. PNG on a full-bleed photo can balloon file size past ESP limits.
• Expired converter downloads: Browser converters and temporary links die. Re-host approved PNGs before the link expires.
• HEIC in email sequences: Recipients on non-Apple clients often cannot preview HEIC. Convert before the sequence builder.
• Broken joins: Conversion succeeds but the asset row never joins to the account table.
• Mixed originals: Phone dumps interleave HEIC and JPEG. Filter by extension before conversion so you do not double-encode existing JPEGs into PNG without reason.
• Dirty export views: Intermediate Clay columns leak into CSV packages. Follow Clay University guidance and build dedicated export views with only raw values that matter.

The end state should feel boring: HEIC archived if needed, PNG masters approved and versioned, JPG deliveries where size matters, and Clay holding only the URLs and status fields multi-channel packages need.