WeTransform can be embedded directly into your website or application — so your clients never need to know WeTransform exists. They upload their files, see the transformation, fix errors, and submit — all within your interface.
There are two integration modes. Choose the one that fits your technical setup.
🖥️ Mode 1 — Embed via iframe (inline)
The iframe mode displays the full WeTransform interface inside your page. Your client never leaves your site — the upload, match, finalize, and submit steps all happen inline.
[📸 ILLUSTRATION: Side-by-side showing a branded website with WeTransform embedded as an iframe panel inside the page]
To embed, point an iframe to your branded WeTransform URL with the appropriate parameters:
<iframe src="https://your-name.send-a-file.io/template-handle?customer_id=1234&signature=..." width="100%" height="800px" frameborder="0" ></iframe>
Every request must include a HMAC SHA256 signature to authenticate the session. See Authentication — how to make the experience seamless for your clients.
🔗 Mode 2 — Redirect to a branded page
Instead of embedding an iframe, you redirect your client to a dedicated WeTransform page at your custom URL: your-company.send-a-file.io. This page displays your logo and colors — it looks like your product.
[📸 ILLUSTRATION: Branded send-a-file.io page showing a company logo, colors, and the WeTransform upload interface]
Once the client submits their file, WeTransform redirects them back to your Return URL with a signed download link — your system receives the transformed file automatically.
⚙️ The WeTransform SDK
For deeper integration, WeTransform provides an SDK that handles the HMAC signature generation, redirection logic, and return URL verification. This abstracts the security layer so your development team doesn't have to implement it from scratch.
For full SDK documentation and code examples in PHP, Python, JavaScript, and more:
🔄 The end-to-end flow
Your client clicks "Upload file" on your platform
Your server generates a signed URL and redirects (or embeds via iframe)
The client uploads their file, reviews errors, and submits
WeTransform redirects to your Return URL with the transformed file URL
Your system downloads the file and integrates it — done
🔁 Webhooks as an alternative. Instead of using the Return URL redirect, you can configure a webhook to receive the file automatically as soon as it's processed — without waiting for the client to complete the flow. See How to receive your output automatically with webhooks.
👉 What to do next