🍳 Embed the Converter

About the FryConvert Widget

The FryConvert embed widget is a free, self-contained tool that lets your readers convert oven temperature and time into recommended air fryer settings without leaving your page. It's the same converter that powers the home page of fryconvert.com — a small iframe with no external dependencies for your visitors and no analytics or tracking added to your site.

It's a good fit if you run a food blog, a recipe site, a cookbook companion page, or any content that talks about adapting recipes. Visitors get the answer in one click; you keep them on your page instead of sending them to a third-party converter and losing the session.

Preview

This is what the widget looks like on your site:

Get the Embed Code

Choose a size and copy the code into your site's HTML.

Choose Size

Embed Code

Installation by Platform

Paste the embed code into any HTML block on your page. Specific instructions for the most common platforms:

WordPress

In the block editor, add a "Custom HTML" block where you want the widget to appear and paste the embed code. In the classic editor, switch to the "Text" tab (not Visual) before pasting. The widget works without any plugins. If you use the Gutenberg theme builder, it also works inside a "Code" block. Page caching plugins like WP Rocket or W3 Total Cache don't need special configuration — the iframe is just inert HTML to them.

Squarespace

Add a "Code" block (not "Embed") to your post or page and paste the iframe code. Squarespace's Code block is enabled by default on Business plans and above. The widget will respect any width constraints set by your section.

Wix

Use the "Embed HTML" element (Add → Embed → Embed HTML / Custom Embeds → Embed a Widget). Paste the iframe code. The widget loads inside Wix's own sandbox iframe, which adds a small extra load time but otherwise works normally.

Ghost & Substack

In Ghost, add an HTML card and paste the code. Substack supports iframe embeds in custom HTML blocks on web-rendered posts; some Substack email templates strip iframes from the email version, so the widget may only appear when readers view the post on the web.

Blogger

Switch to the "HTML view" of your post editor and paste the code where you want the widget to appear. Then switch back to "Compose view" to continue writing your post.

Plain HTML and static sites

For Jekyll, Hugo, Next.js, Astro, 11ty, or any other static-site framework, paste the iframe tag directly into your Markdown or HTML source. No build configuration is needed. Most static-site frameworks pass raw HTML through to the rendered page without modification.

Customization Options

The size buttons above let you pick between fixed widths (350×380, 450×400) or a full-width version that fills its container. A few additional tweaks you can make directly on the iframe attributes:

• Border radius: Adjust the border-radius value in the inline style to match your site's design language. Set it to 0 for square corners.
• Shadow: Remove or adjust the box-shadow in the inline style. The default is a subtle drop shadow that works on light backgrounds; if your site has a dark theme, replace with 0 2px 10px rgba(255,255,255,0.05) or remove it entirely.
• Lazy loading: The default code includes loading="lazy" so the widget doesn't load until a reader scrolls near it. Remove this attribute if you want it to render immediately (rarely the right choice — lazy loading is almost always what you want).
• Title: The title attribute is used by screen readers. Leave the default or change it to match your section heading for better accessibility.

The widget does not currently support theming via URL parameters — colors and fonts match the FryConvert brand. If your site has a strong visual identity that clashes, wrapping the iframe in a styled container with a header that matches your design usually solves it.

Why Add This Widget?

Your readers will love it

Visitors to your recipe posts can instantly convert oven instructions to air fryer settings without leaving your page. It's a small thing, but it removes one of the most common friction points in recipe blogging: the recipe says 425°F for 30 minutes in the oven, the reader wants to use their air fryer instead, and now they don't have to open a new tab to figure out the conversion.

Completely free, no strings

No signup, no API key, no rate limits, no ads injected into your page, no surprise paid tier later. The widget is a single iframe loading static HTML, JavaScript, and CSS from fryconvert.com. We pay for the bandwidth through display ads on our own pages — not yours.

Mobile friendly

The widget is fully responsive and works on any screen size down to about 280 pixels wide. The full-width version is the safest choice if you don't know what device your readers will be on, since it'll scale to whatever container you put it in.

Fast and lightweight

The widget itself weighs about 6 KB of HTML plus a small JS payload for the converter logic. With the default loading="lazy" attribute, it doesn't load at all unless a reader scrolls near it — meaning effectively zero impact on your page's Core Web Vitals scores.

Accessible by default

The widget uses native form controls, semantic HTML, and proper ARIA labels. It works with keyboard navigation and standard screen readers (NVDA, JAWS, VoiceOver) without any extra configuration on your end.

Embedding FAQ

Will this slow down my page?

No. The iframe uses loading="lazy" by default, so the widget only loads when a reader scrolls near it. Your initial page load is unaffected, and the widget itself loads in well under a second on a normal connection.

Do I need to give credit?

The widget already includes a small "FryConvert" link at the bottom of the converter — that's all the credit we ask for. You don't need to add separate attribution to your post or page.

Can I remove the FryConvert branding inside the widget?

No, the in-widget link to fryconvert.com is part of the terms of use for the free embed. It's how we justify the bandwidth costs of the free tier. The link is small and non-intrusive.

Does the widget collect data from my visitors?

The widget itself doesn't store data, set cookies, or send personal information anywhere. Standard server logs from the iframe request (IP address, user agent, referer header) are logged by our hosting provider for security and analytics — same as any third-party embed you'd use.

Is it GDPR / CCPA compliant for my readers?

The widget doesn't set cookies and doesn't transmit personally identifying information beyond what's contained in a standard HTTP request. Whether your overall page complies with privacy regulations depends on your site as a whole, but the embed itself isn't a compliance risk.

Can I modify the widget's code or fork it?

The embed terms permit you to use the widget as-is. You're not licensed to copy the widget's source code and host it yourself, modify the converter logic, or strip out the FryConvert link. If you need a custom version — white-label, different brand colors, additional foods — contact us at hello@fryconvert.com.

What happens if FryConvert goes down or shuts down?

The iframe would show a broken state to your readers. We've been running with high uptime, but no embed is fully safe from this risk. If you want a self-hosted converter you control end-to-end, the simplest fallback is to publish the conversion math directly in your post: subtract 25°F from the oven temperature and reduce the cook time by about 20%. The widget automates that math.

Can I embed multiple instances on one page?

Yes. The widget is fully isolated inside its iframe, so multiple copies on the same page don't interfere with each other. Most sites only need one, but recipe roundup pages sometimes embed one near each individual recipe.