IntlPull Figma Plugin: The Free Tool That Makes Multilingual Design Actually Work

Introduction

Every team building for a global audience hits the same wall: designs look perfect in English, but nobody knows how they'll hold up in German, Japanese, or Arabic until it's too late.

The typical localization workflow is broken. Designers create mockups in English. Product managers copy text into spreadsheets. Developers extract strings into JSON files. Translators work in a completely separate tool with zero visual context. Then, weeks later, QA discovers that "Submit" became "Absenden" and broke the button layout.

This back-and-forth costs teams thousands of hours every year. According to CSA Research, companies spend an average of 23% of their localization budget on rework caused by lack of visual context during translation.

IntlPull's Figma plugin eliminates this chaos. It creates a direct, bidirectional connection between your Figma design files and your translation management system. Designers preview any language with one click. Writers see their copy in context. Translators get visual context. Developers get clean keys that sync to their codebase. Everyone stays in sync.

Here's what makes IntlPull different: the Figma plugin is completely free on all plans—including our free tier. No "upgrade to unlock" walls. No enterprise-only features. A solo freelancer gets the exact same capabilities as a Fortune 500 team.

The Problem with "Free" Plugins That Aren't Really Free

Let's be honest about how most TMS companies use their Figma plugins.

The plugin is free to install. A designer gets frustrated with copy-pasting and installs it. They become the internal champion, showing the team how visual context helps translators. Everything works great—until the team wants to actually automate the workflow.

Then they hit the wall:

• Want to push keys to GitHub? Upgrade to Pro ($140+/month)
• Need AI batch translations? Enterprise tier
• SSO for your team? Enterprise tier
• More than 3 users? Time to talk to sales

The "free" plugin was never free. It was a lead generation tool designed to get you hooked before revealing the real price.

IntlPull works differently. Our Figma plugin connects to the same platform that powers our CLI, API, and OTA updates. The free tier includes:

• Full Figma plugin functionality
• CLI for developers (npx @intlpullhq/cli sync)
• REST API access
• AI translation credits
• Unlimited team members

No bait-and-switch. No "contact sales" for basic features.

Who Benefits from This Plugin?

UI/UX Designers

You spend hours perfecting layouts, spacing, and typography. Then translations arrive and everything breaks. German text is 30% longer than English. Japanese needs different line heights. Arabic flips the entire layout.

With IntlPull's plugin, you can:

• Preview any language instantly: One click switches your entire design to German, Japanese, Arabic, or any of 50+ supported languages
• Catch layout issues before handoff: See exactly which buttons overflow, which headlines wrap awkwardly, which cards need more padding
• Design for the longest string: German and Finnish are notoriously verbose—now you can design with real translated text, not guesses
• Test RTL layouts: Arabic and Hebrew flip your entire interface—preview this in Figma, not in production
• Export localized mockups: Deliver design specs, prototypes, and assets in every target language

Real example: A fintech designer discovered their "Transfer Money" button worked perfectly in English but became "Geld überweisen" in German—too long for the button width. They caught this in Figma, adjusted the layout once, and shipped a design that worked for all 12 target languages.

Developers (Yes, This Plugin Is for You Too)

Most Figma localization plugins are designed for designers and ignore the developer experience. IntlPull is different—we built the platform for developers first, then added the Figma plugin.

Here's why developers love it:

• Keys sync to your codebase: Push from Figma, pull with CLI. Same keys, same structure.
• No more "what did the designer call this?": Key names in Figma match your en.json
• Works with your stack: React, Next.js, Vue, React Native, Flutter—we have SDKs
• CI/CD integration: npx @intlpullhq/cli sync in your pipeline
• MCP support: Your AI coding assistant (Cursor, Claude) can manage translations directly

TerminalCopy
1# Developer workflow
2npx @intlpullhq/cli pull              # Get latest translations
3npx @intlpullhq/cli push              # Push new keys from code
4npx @intlpullhq/cli sync --watch      # Real-time bidirectional sync

The Figma plugin and CLI share the same project. When a designer pushes "checkout.submit_button" from Figma, it appears in your next npx @intlpullhq/cli pull.

Technical Writers & Documentation Teams

Your job is precision. Every word matters. Every label must be clear, consistent, and correctly placed.

The plugin transforms your workflow:

• Write copy in context: See exactly how your microcopy looks in the actual interface
• Push directly from designs: No more copying text into spreadsheets
• Maintain terminology consistency: Keys link to your glossary automatically
• Review translations visually: See how your carefully crafted error messages look in every language
• Track translation status: Visual indicators show which text is linked and which needs attention

Marketing & Creative Teams

Global campaigns require localized assets—fast. You're creating social media graphics, email headers, landing page mockups, and ad creatives for multiple markets simultaneously.

IntlPull accelerates your creative workflow:

• Localize marketing assets in minutes: Push poster text, pull back translations, export
• Preserve your typography: Bold text, custom fonts, and formatting styles stay intact
• Handle dynamic content: Variables like {{product_name}} or {{discount}} work seamlessly
• Batch process entire campaigns: Select 50 frames, push all text at once

Real example: An e-commerce marketing team localized their Black Friday campaign (127 assets across 8 languages) in a single afternoon. Previously, this took their agency two weeks and $5,000.

Creating Multi-Language Posters, Banners & Visual Assets

One of the most powerful use cases for IntlPull's Figma plugin is creating localized visual marketing assets at scale. Whether you're designing event posters, web banners, social media graphics, or print materials, the plugin transforms what used to be a tedious manual process into a streamlined workflow.

The Old Way vs. The IntlPull Way

Traditional poster/banner localization:

1. Design the English version
2. Duplicate the file for each language
3. Manually replace text in each duplicate
4. Adjust layouts individually when text doesn't fit
5. Export each version separately
6. Repeat for every design update

With IntlPull:

1. Design once
2. Push all text with one click
3. Preview any language instantly
4. Export all language versions in seconds

Step-by-Step: Multi-Language Poster Creation

1. Design Your Master Asset

Create your poster or banner in your primary language. Use Figma's auto-layout where possible—this ensures your design adapts gracefully when text length changes across languages.

Pro tip: Design with German or Finnish text in mind. These languages are typically 30-40% longer than English, so if your layout works for German, it'll work for everything.

2. Push Text to IntlPull

Select your poster frame and open the IntlPull plugin:

1. Go to the Push tab
2. The plugin automatically detects all text nodes: headlines, body copy, CTAs, fine print
3. Review the detected text and assign meaningful key names (e.g., poster.headline, poster.cta_button, poster.event_date)
4. Click Push Keys

The plugin captures a screenshot with bounding boxes, giving translators visual context for every string.

3. Translate (AI or Human)

From the IntlPull dashboard, you have options:

• AI Translation: One-click translation to 50+ languages using GPT-4, Claude, or DeepL
• Human Translation: Assign to your team or professional translators who see your poster design alongside each string
• Hybrid: AI for first draft, human review for polish

4. Preview Languages in Figma

Back in Figma, use the Translate tab:

1. Select your target language from the dropdown
2. Click Switch Language
3. Watch your poster transform instantly

Check for:

• Text overflow or truncation
• Awkward line breaks
• Layout issues with longer/shorter text
• RTL layout for Arabic, Hebrew, Farsi

5. Multi-Language Preview (Side-by-Side)

Need to see multiple languages at once? Use the Multi-Language Preview feature:

1. Select your poster frame
2. Open Multi-Language Preview panel
3. Choose languages to compare (e.g., English, German, Japanese, Arabic)
4. The plugin generates side-by-side previews

This is invaluable for:

• Stakeholder reviews
• Ensuring brand consistency across markets
• Catching layout issues before export

6. Batch Export All Languages

Ready to export? The plugin supports batch export:

1. Select your poster frame(s)
2. Go to Export tab
3. Select target languages
4. Choose format (PNG, JPG, PDF, SVG)
5. Click Export All

You'll get poster-en.png, poster-de.png, poster-ja.png, etc.—all in seconds.

Real-World Examples

Event Posters

A conference organizer needed promotional posters in 12 languages for their global tech summit. Using IntlPull:

• Time to localize: 45 minutes (vs. 3 days manually)
• Languages: English, German, French, Spanish, Portuguese, Italian, Dutch, Polish, Japanese, Korean, Chinese (Simplified), Arabic
• Assets created: 36 poster variants (3 sizes × 12 languages)

Social Media Banners

A SaaS company runs campaigns across 8 markets. Each campaign includes:

• LinkedIn banners (3 sizes)
• Twitter/X headers
• Facebook covers
• Instagram posts and stories

Before IntlPull: 2 designers, 1 week per campaign After IntlPull: 1 designer, 1 day per campaign

E-commerce Promotional Banners

An online retailer creates weekly promotional banners for their homepage. With IntlPull:

1. Designer creates the English banner
2. Pushes text: "Summer Sale - Up to 50% Off", "Shop Now", "Ends Sunday"
3. AI translates to 6 languages in seconds
4. Designer previews each language, adjusts one layout issue in German
5. Exports all versions
6. Total time: 15 minutes for 6 languages

Print Materials

IntlPull works just as well for print assets:

• Trade show banners
• Product packaging mockups
• Brochures and flyers
• Retail signage

Export as PDF with bleed marks, and your print vendor gets production-ready files in every language.

Handling Complex Banner Scenarios

Dynamic Content & Variables

Your banner says "Save $50 on {{product_name}}"? IntlPull handles this:

• The plugin detects {{product_name}} as a variable
• Translators see the variable placeholder, not a hardcoded value
• When you preview, you can test with different product names

Multiple Text Styles

Posters often have mixed typography—bold headlines, italic taglines, different font sizes. IntlPull preserves all styling:

• Font family and weight
• Text size and line height
• Colors and effects
• Text alignment

When you pull translations, your typography stays intact.

Responsive Banner Sets

Creating banners in multiple sizes (leaderboard, skyscraper, square)?

1. Design all sizes with the same key names
2. Push once—all sizes share the same translations
3. Pull translations—all sizes update simultaneously

No duplicate translation work, no inconsistencies between sizes.

Tips for Poster & Banner Localization

1. Use auto-layout: Figma's auto-layout makes text expansion painless
2. Set text truncation rules: Decide upfront how to handle overflow (ellipsis, smaller font, multi-line)
3. Test extremes: Preview in German (long) and Chinese (short) to catch edge cases
4. Consider cultural adaptation: Some markets may need different imagery or color schemes—IntlPull handles the text, you handle the creative
5. Version control: Use IntlPull's tagging to track campaign versions (e.g., black-friday-2026, summer-sale-v2)
6. Batch operations: Select multiple frames to push/pull all at once—huge time saver for large campaigns

Dynamic Localized Content: Serving HTML & Images by User Locale

Here's where things get really powerful. Instead of just exporting static assets, you can use IntlPull to dynamically serve localized banners, posters, and rich HTML content to users based on their locale—in real-time.

The Concept: Locale-Aware Content Delivery

Traditional approach: Export 12 banner images, upload each to your CDN, write conditional logic to serve the right one.

IntlPull approach: Design once in Figma, push to IntlPull, and let our API serve the right content automatically based on the user's locale.

Use Case 1: Dynamic Localized Images

Serve locale-specific banner images without managing dozens of files:

JSXCopy
1// React component - banner automatically matches user locale
2import { useLocale } from '@intlpullhq/react';
3
4function PromoBanner() {
5  const { locale } = useLocale();
6  
7  return (
8    <img 
9      src={`https://cdn.intlpull.com/assets/promo-banner?locale=${locale}&project=your-project`}
10      alt={t('promo.banner_alt')}
11    />
12  );
13}

The IntlPull CDN automatically serves promo-banner-de.png for German users, promo-banner-ja.png for Japanese users, etc.—all from a single URL pattern.

Use Case 2: Localized HTML Snippets

Need to serve rich, styled content that varies by locale? Think email headers, in-app announcements, or marketing blocks with complex formatting.

JSXCopy
1// Fetch localized HTML content dynamically
2const LocalizedAnnouncement = () => {
3  const { locale } = useLocale();
4  const [html, setHtml] = useState('');
5
6  useEffect(() => {
7    fetch(`https://api.intlpull.com/v1/content/announcement?locale=${locale}`)
8      .then(res => res.json())
9      .then(data => setHtml(data.html));
10  }, [locale]);
11
12  return <div dangerouslySetInnerHTML={{ __html: html }} />;
13};

The HTML content is managed in IntlPull—designers update it in Figma, translators localize it, and your app always serves the latest version.

Use Case 3: Locale-Specific Landing Page Sections

Serve entire page sections that adapt to the user's market:

TypeScriptCopy
1// Next.js API route example
2import { IntlPull } from '@intlpullhq/node';
3
4export async function GET(request: Request) {
5  const locale = request.headers.get('accept-language')?.split(',')[0] || 'en';
6  
7  const content = await IntlPull.getLocalizedContent({
8    key: 'homepage.hero_section',
9    locale,
10    format: 'html', // or 'json', 'markdown'
11  });
12
13  return Response.json({ 
14    html: content.html,
15    images: content.assets, // Associated localized images
16  });
17}

Use Case 4: Email Campaign Personalization

Send emails with localized banners and content blocks:

TypeScriptCopy
1// Email service integration
2const sendLocalizedEmail = async (user: User) => {
3  const locale = user.preferredLocale;
4  
5  // Get localized email assets from IntlPull
6  const emailContent = await IntlPull.getEmailAssets({
7    template: 'welcome-email',
8    locale,
9  });
10
11  await emailService.send({
12    to: user.email,
13    subject: emailContent.subject,
14    html: emailContent.body,
15    // Banner image URL automatically localized
16    headerImage: emailContent.assets.headerBanner,
17  });
18};

Use Case 5: A/B Testing Localized Creatives

Test different banner designs across markets:

JSXCopy
1// Serve different creative variants by locale + experiment
2function ExperimentalBanner() {
3  const { locale } = useLocale();
4  const variant = useExperiment('banner-test'); // 'A' or 'B'
5  
6  return (
7    <img 
8      src={`https://cdn.intlpull.com/assets/hero-banner?locale=${locale}&variant=${variant}`}
9      alt={t('hero.banner_alt')}
10    />
11  );
12}

Designers create variant A and B in Figma, push both to IntlPull, and your experimentation platform handles the rest.

The Figma-to-Production Pipeline

Here's how it all connects:

1. Designer creates banner in Figma → Uses IntlPull plugin to push text
2. Translations happen → AI or human translators work with visual context
3. Designer exports localized versions → Plugin batch-exports all language variants
4. Assets upload to IntlPull CDN → Automatic via plugin or CI/CD
5. App requests content → IntlPull API serves the right locale automatically
6. User sees localized content → Zero conditional logic in your codebase

API Endpoints for Dynamic Content

IntlPull provides several endpoints for dynamic content delivery:

TerminalCopy
1# Get localized image URL
2GET /v1/assets/{asset-key}?locale=de
3
4# Get localized HTML content
5GET /v1/content/{content-key}?locale=ja&format=html
6
7# Get all assets for a campaign
8GET /v1/campaigns/{campaign-id}/assets?locale=fr
9
10# Batch fetch multiple localized assets
11POST /v1/assets/batch
12{
13  "keys": ["hero-banner", "promo-card", "footer-cta"],
14  "locale": "es"
15}

CDN Integration

IntlPull's CDN automatically handles:

• Locale detection: Accept-Language header parsing
• Fallback logic: Serve English if requested locale unavailable
• Cache optimization: Edge caching for fast delivery worldwide
• Image optimization: WebP/AVIF conversion, responsive sizes

HTMLCopy
1<!-- Simple HTML integration -->
2<picture>
3  <source 
4    srcset="https://cdn.intlpull.com/assets/banner?locale=auto&format=webp" 
5    type="image/webp"
6  >
7  <img 
8    src="https://cdn.intlpull.com/assets/banner?locale=auto" 
9    alt="Promotional banner"
10  >
11</picture>

The locale=auto parameter tells the CDN to detect the user's locale from their browser settings.

Real-World Implementation: E-commerce Homepage

An e-commerce site serving 8 markets implemented dynamic localized banners:

Before:

• 8 separate banner images manually uploaded
• Conditional logic in React to select the right one
• Cache invalidation headaches when updating
• 3-day turnaround for banner updates

After with IntlPull:

• Single Figma file, push once
• One <img> tag with locale parameter
• CDN handles caching and invalidation
• 30-minute turnaround for banner updates

JSXCopy
1// Their entire banner component
2const HomepageBanner = () => (
3  <img 
4    src="https://cdn.intlpull.com/assets/homepage-hero?locale=auto&v=2"
5    alt={t('homepage.hero_alt')}
6    className="w-full"
7  />
8);

Benefits of Dynamic Localized Content

1. Single source of truth: Figma design → IntlPull → All platforms
2. No code changes for updates: Designers update, users see changes immediately
3. Reduced bundle size: Images loaded from CDN, not bundled in app
4. Consistent branding: Same assets across web, mobile, email
5. Faster iteration: Update a banner in Figma, live in production in minutes
6. Analytics integration: Track which localized assets perform best

The Full Stack: Figma + CLI + API + OTA

Here's what makes IntlPull fundamentally different from Lokalise, Crowdin, or Phrase: the Figma plugin is just one entry point into a complete developer platform.

For Design-Led Teams

Designer pushes from Figma → Keys appear in IntlPull dashboard → AI translates or human translator works (with visual context) → Designer previews in Figma → Developer pulls with CLI → Keys in codebase, ready to ship

For Developer-Led Teams

Developer adds keys in code → npx @intlpullhq/cli push → Keys appear in IntlPull dashboard → Designer links Figma text to existing keys → Translator works with visual context → npx @intlpullhq/cli pull → Translations in codebase

For Mobile Teams (OTA Updates)

This is where IntlPull really shines. We're the only TMS with native Over-The-Air translation updates for mobile apps.

SwiftCopy
// iOS - translations update without App Store release
let label = IntlPull.t("welcome.message")

KotlinCopy
// Android - no new APK needed
val text = IntlPull.t("welcome.message")

Fix a translation typo? Push it live in seconds. Launch a new language? No app update required. A/B test different copy? Change it server-side.

No other TMS offers this. Not Lokalise. Not Crowdin. Not Phrase.

Why IntlPull Beats the "Enterprise" Alternatives

Pricing That Makes Sense

IntlPull's paid plans start at $12/month for 5,000 keys. That's 85-90% less than Lokalise for equivalent functionality.

Features That Actually Ship

The MCP Advantage (For AI-First Teams)

If you're using Cursor, Claude, or any AI coding assistant, IntlPull's MCP (Model Context Protocol) support is a game-changer.

Your AI can:

• List all translation keys in your project
• Add new keys with translations
• Update existing translations
• Check translation coverage
• Suggest missing translations

No other TMS has this. It's not on Lokalise's roadmap. It's not on Crowdin's roadmap. IntlPull is the only TMS your AI coder can actually use.

Smart Features That Save Hours

Intelligent Variable Detection

Most plugins treat "Hello, Sarah" as a static string. IntlPull recognizes it matches the pattern "Hello, {{name}}" and:

1. Links to your existing translation key
2. Extracts "Sarah" as the variable value
3. Interpolates correctly in every language

This extends to complex patterns:

• "You have {{count}} items" — Numeric variables
• "{{user}} commented on {{item}}" — Multiple variables
• "Sale ends {{date}}" — Date placeholders

Three-Tier Key Matching

When you push text from Figma, the plugin uses intelligent matching:

1. Exact Match: "Submit Order" matches existing key submit_order
2. Template Match: "Hello, John" matches pattern "Hello, {{name}}"
3. Fuzzy Match: "Submitt Order" (typo) suggests submit_order with 95% confidence

No more duplicate keys cluttering your translation memory.

Conflict Detection

Made local edits in Figma? The plugin notices and asks you to choose: overwrite with remote translation or keep your local changes. You're always in control. No surprises.

Automatic Screenshot Context

When you push text, the plugin captures a screenshot with bounding boxes showing exactly where each string appears. Translators see the visual context, leading to better translations that actually fit your design.

Real-World Time Savings

Solo Designer / Small Team

Before IntlPull:

• Design in English
• Export text to spreadsheet
• Send to translator
• Wait for translations
• Manually update Figma
• Time: 2-3 hours per screen, per language

With IntlPull:

• Push text (30 seconds)
• AI translates instantly
• Pull translations (10 seconds)
• Time: 5 minutes per screen, all languages

Enterprise Team

Before IntlPull:

• Designer creates mockups (Week 1)
• PM extracts strings to Jira (Week 1)
• Localization team translates (Weeks 2-3)
• Dev integrates translations (Week 3)
• QA finds layout issues (Week 4)
• Timeline: 4 weeks per release

With IntlPull:

• Designer pushes from Figma (Day 1)
• Translator works with visual context (Days 2-5)
• Designer previews all languages (Day 5)
• Dev pulls with CLI (Day 6)
• Timeline: 1 week per release

The ROI Math

For a team spending $140/month on Lokalise:

• Switch to IntlPull Growth ($79/month): Save $732/year
• Plus: OTA updates, MCP support, faster workflows

For a team with 10 languages and weekly releases:

• 3 weeks saved per release × 52 releases = 156 weeks of engineering time saved annually

Getting Started in 5 Minutes

Step 1: Install the Plugin

1. In Figma: Plugins → Browse plugins in Community
2. Search "IntlPull"
3. Click Install

Step 2: Connect Your Account

1. Open the plugin in any Figma file
2. Click Sign in with IntlPull
3. Approve in your browser
4. Select your project

No account yet? Create one free—no credit card required.

Step 3: Push Your First Text

1. Select a frame with text
2. Go to Push tab
3. Review detected nodes
4. Click Push Keys

Step 4: See It in Another Language

1. Go to Translate tab
2. Pick a language
3. Click Switch Language
4. Watch your design transform

Step 5: Sync to Your Codebase (Developers)

TerminalCopy
npm install -g @intlpullhq/cli
npx @intlpullhq/cli login
npx @intlpullhq/cli pull

Your translations are now in locales/en.json, locales/de.json, etc.

Best Practices

For Designers

• Name frames descriptively: "Checkout - Payment Form" helps translators more than "Frame 47"
• Design for text expansion: German is 30% longer than English
• Use auto-layout: Components resize gracefully when text length changes
• Test RTL early: Preview Arabic/Hebrew layouts before development

For Developers

• Use the CLI in CI/CD: npx @intlpullhq/cli pull before every build
• Enable watch mode locally: npx @intlpullhq/cli sync --watch for real-time sync
• Leverage MCP: Let your AI assistant handle routine translation tasks

For Teams

• Push early: Don't wait for "final" designs—translators can work in parallel
• Use tags: Organize by version, feature, or platform
• Review in Figma: Use comments for translation feedback with visual context

Frequently Asked Questions

Does the plugin work with Figma's free plan?

Yes. The IntlPull plugin works with any Figma account—Free, Professional, or Enterprise.

What languages are supported?

50+ languages including RTL (Arabic, Hebrew, Farsi). The plugin handles text direction automatically.

Can I migrate from Lokalise/Crowdin/Phrase?

Yes. Run npx @intlpullhq/cli migrate --from lokalise and your translations, TM, and glossary transfer in minutes.

Is there a catch with the free tier?

No catch. Free tier includes 500 keys, unlimited users, full Figma plugin, CLI, and API access. We make money when teams grow and upgrade—not by locking basic features.

How is this different from Lokalise's Figma plugin?

1. Actually free: No paywall for automation features
2. Developer-first: CLI and API included on free tier
3. OTA updates: Push translations to mobile apps without app store releases
4. MCP support: Your AI coding assistant can manage translations
5. 85-90% cheaper: $79/month vs $140+/month for equivalent features

What's Next

We're constantly shipping:

• Figma Variables Integration: Sync with Figma's native variables
• Component-Level Linking: Link entire components, not just text
• Side-by-Side Preview: See multiple languages simultaneously
• Figma Dev Mode: Surface keys directly in Dev Mode

The Bottom Line

The localization industry has been charging enterprise prices for basic functionality. Figma plugins locked behind paywalls. CLIs that require "Pro" plans. APIs that need "Enterprise" contracts.

IntlPull is different. We built a complete localization platform—Figma plugin, CLI, API, OTA, MCP—and made the core functionality free. We grow when you grow.

For designers: Preview any language in your actual design with one click.

For developers: Sync translations to your codebase with npx @intlpullhq/cli pull.

For mobile teams: Push translation updates without app store releases.

For AI-first teams: Let Claude or Cursor manage your translations via MCP.

For everyone: Stop paying $140/month for features that should be free.

Ready to try a TMS that respects your time and budget?

Install the Figma Plugin · Create Your Free Account · Compare IntlPull vs Lokalise