Inventory every destination and image before the campaign leaves.

What does the email link and asset preflight do?

Extract links and image sources, then flag empty destinations, malformed or relative URLs, HTTP assets, duplicate destinations, tracking parameters, missing image dimensions, and ambiguous clickable content. The immediate result is a copyable email link and asset inventory with pre-send warnings. That makes the tool useful when a focused question needs an answer before a file is handed off, a campaign is trafficked, or a production workflow begins.

The scope is intentionally narrow. It is designed for solving one focused email-production problem, not for replacing the complete production process. A useful result should make the next decision clearer while leaving the original file, design, or workflow under the user’s control.

Your files and inputs are processed locally in this browser and are not uploaded to Hypermatic. Local processing reduces unnecessary data exposure, but it does not remove the need to follow the privacy, confidentiality, and retention requirements that apply to the source material.

How should the email link and asset preflight be used?

Start with the same input that will be used in production whenever possible. Draft content, substitute files, and approximate dimensions can be useful during exploration, but the final check should use the actual export, final copy, destination, or supported range.

Work through the steps in order and keep the generated result beside the source. If the result identifies a warning, decide whether it is a real production problem, an acceptable tradeoff, or a limitation of a browser-based inspection before changing the underlying work.

• Paste or upload the ESP-ready HTML.
• Review every destination, image source, protocol, duplicate, tracking value, and structural warning.
• Open important destinations, send a tracked test, and repeat the audit on delivered HTML.

How should the result be interpreted?

A browser tool can make measurable signals visible, but it cannot reproduce every application, platform, rendering engine, policy, or team constraint. Treat the report as evidence for a decision rather than a universal guarantee. The strongest verification is the final HTML in the email platforms and client environments the campaign must support.

Pay particular attention to edge cases that are easy to miss during a quick check: unusual fonts, long or localized content, hidden metadata, external dependencies, different aspect ratios, browser-specific behavior, and last-minute source changes. Re-run the tool whenever the production input changes materially.

• Relative URLs often break after an email leaves the authoring environment.
• Tracking systems can rewrite URLs after this local scan.
• Check unsubscribe and preference links in a real campaign because template variables may only resolve at send time.

Common questions about email link and asset preflight

Does the checker visit every URL? No. It audits URL structure locally. Browser security, authentication, rate limits, bot protection, and campaign-only template variables make a universal availability check unreliable.

Are mailto, telephone, and anchor links allowed? Yes. They are inventoried separately because their behavior and testing requirements differ from ordinary HTTPS destinations.

Is the email link and asset preflight free? Yes. You can use it without an account or signup. The focused result is generated directly in your browser.

When does Emailify become the better workflow?

The free tool is the right choice for a quick individual check, calculation, preview, or template. It remains useful even if the task only occurs once and no broader production workflow is needed.

Emailify becomes more practical when the same job turns into designing responsive campaigns and exporting production-ready email HTML from Figma. At that point, keeping the work close to the Figma source reduces repeated exports, copy-and-paste steps, inconsistent decisions, and handoff drift.

Before adopting any workflow, compare the time spent on the recurring manual process with the setup and review required by the tool. The goal is not to add another application; it is to remove repetitive work while preserving the quality checks that still need human judgment.