Unlayer Support Guide: Troubleshoot Common Issues & Get Help

Running into issues with Unlayer? You’re not alone. We’ve put this guide together to help you just with that. 

Think of it as your go-to Unlayer support hub, where we’ve gathered all the essentials from the Unlayer help center in one place.

Here, you’ll find quick answers to the most common problems, plus direct links to in-depth troubleshooting guides for React, Angular, and Vue.

And if you still need further assistance, we’ll also show you how to reach Unlayer customer support for personalized help.

Let’s get started!

Unlayer Common Issues Overview

When integrating Unlayer into your projects/platforms (especially in React, Angular, or Vue), certain issues tend to pop up again and again. 

Below are the most frequent Unlayer support themes developers face — quick to spot, usually quick to fix — and pointers to where you can go for deeper help.

✅ Helpful resources

If you’d like to dig deeper into specific issues, here are some official Unlayer resources worth bookmarking:

• Installation Guide – for setup and embedding basics.

• Version Management – to lock, update, or roll back versions safely.

• File Manager Documentation – for handling media storage conflicts.

• How to White-Label the Embeddable Editor – make the editor match your brand.

• Custom Tools Guide – to create and troubleshoot custom blocks.

Unlayer Not Loading? Display & Setup Issues

When Unlayer doesn’t load correctly, the editor goes blank, or certain blocks fail to render, the problem almost always traces back to setup or initialization misconfigurations. 

Unlike other parts of the workflow, Unlayer doesn’t throw error codes during initialization or export, so most of the issues show up in how the editor behaves rather than through system messages.

Common causes & quick Fixes

Special case: “User not provided” error

In rare cases, users may see a “User not provided” error when trying to load the editor.

Why it happens: 

This typically occurs when Identity Verification has been enforced on the project. In such cases, the editor requires user information (security signature) to authenticate the session.

Resolution: 

Pass a security signature when initializing the editor. You can find step-by-step instructions in Unlayer’s Identity Verification Guide.

📌 Key takeaway

Most display and setup issues in Unlayer boil down to initialization missteps. 

Since Unlayer doesn’t throw error codes during initialization or export, watch for subtle signs, like missing blocks, blank screens, or failed authentications to know when configuration needs adjustment.

Resolving Unlayer Export & Delivery Issues

Exporting designs is one of the most critical steps when working with Unlayer, whether you’re sending emails, embedding templates into your app, or delivering HTML to an ESP. 

But sometimes, export requests don’t behave as expected.

🔑 Common export problem: “Unauthorized” error

One frequently reported issue is seeing an “Unauthorized” error when using the Export Cloud API.

Why does it happen?

This error usually occurs when the export request is made from a plan that does not include access to the Export Cloud API. 

For example, if you’re on a Free Legacy or Legacy Startup plan, this feature isn’t supported.

Resolution:

The fix here isn’t technical; it’s account-related. To gain access, you’ll need to:

1. Upgrade to a current paid plan.
   Paid plans include Export Cloud API access by default.

2. Confirm feature availability.
   Check that your plan supports the specific export endpoints you’re calling.

Once you’re on an eligible plan, the restriction is lifted, and your export requests should work seamlessly.

Framework-Specific Troubleshooting Resources

Every framework has its own quirks when working with Unlayer. Instead of cramming all solutions here, here’s a quick overview of the most common issues across React, Angular, and Vue. Plus, links to full troubleshooting guides for in-depth fixes.

🔵 React: Embedding issues & display errors

Integrating Unlayer into a React app often leads to hiccups with initialization, configuration, or certain blocks not rendering. 

Developers also run into problems like:

• Improper initialization when everything is dumped inside App.js instead of modular components.

• AMP/Carousel blocks not showing because AMP mode wasn’t enabled in the config.

• Version mismatches leading to unstable behavior.

• HTML templates not loading since Unlayer only accepts JSON by default.

Example: Enabling AMP for React

<EmailEditor 
        ref={emailEditorRef} 
        onReady={onReady} 
        options=
        {{
            projectId: 123456, // Replace with your actual Unlayer project ID
            displayMode: “email”, // replace with "web", or "document", or "popup"
            version: 'latest',
            amp: true,
            }}
 />

👉 Full details in the React Troubleshooting Guide.

🟠 Angular: Development pitfalls & fixes

Angular projects come with their own integration challenges due to lifecycle hooks, template rendering, and state management. 

Common pitfalls include:

• Editor not rendering correctly due to Angular’s change detection.

• Exporting designs breaking when state isn’t managed properly.

• Lifecycle conflicts that reinitialize components unexpectedly.

• Breaking changes with Angular updates not aligned with Unlayer configs.

Example: Embedding Unlayer in Angular

import { Component } from '@angular/core';
import { isPlatformBrowser, CommonModule, NgIf } from '@angular/common';
import { EmailEditorModule } from 'angular-email-editor';
@Component({
 selector: 'app-root',
 standalone: true,
 imports: [EmailEditorModule],
 template: `
   <email-editor
     [options]="editorOptions"
     (onLoad)="editorLoaded()"
     (onReady)="editorReady($event)">
   </email-editor>
 `,
})
export class AppComponent {
 editorOptions = {
               // provide Unlayer parameters here
 };
 
editorLoaded() {
   console.log('Editor loaded');
 }
 editorReady(unlayer: any) {
   console.log('Editor is ready', unlayer);
 }
}

👉 More fixes are in the Angular Development Pitfalls and Fixes Guide.

🟢 Vue: Builder export & integration issues

Vue developers often hit snags around reactivity and export workflows. 

Common issues include:

• Export bugs where designs don’t save or render properly.

• Integration conflicts with Vue’s reactive system when binding.

• Styling inconsistencies due to mismatched configs.

• Performance bottlenecks when Unlayer isn’t optimized for Vue components.

Example: Using Unlayer in Vue

<template>
  <div id="app">
    <div class="container">
      <div id="bar">
        <h1>Vue Email Editor (Demo)</h1>
        <button v-on:click="saveDesign">Save Design</button>
        <button v-on:click="exportHtml">Export HTML</button>
      </div>
      <EmailEditor
        :appearance="appearance"
        :min-height="minHeight"
        :project-id="projectId"
        :locale="locale"
        :tools="tools"
        :options="options"
        ref="emailEditor"
        v-on:load="editorLoaded"
      />
    </div>
  </div>
</template>
<script>
  import { EmailEditor } from 'vue-email-editor';
  export default {
    name: 'app',
    components: {
      EmailEditor,
    },
    data() {
      return {
        minHeight: '1000px',
        locale: 'en',
        projectId: 123456, // replace with your project id
        tools: {
          // disable image tool
          image: {
            enabled: false,
          },
        },
        options: {},
        appearance: {
          theme: 'dark',
          panels: {
            tools: {
              dock: 'right',
            },
          },
        },
      };
    },
    methods: {
      editorLoaded() {
        // Pass your template JSON here
        // this.$refs.emailEditor.editor.loadDesign({});
      },
      saveDesign() {
        this.$refs.emailEditor.editor.saveDesign((design) => {
          console.log('saveDesign', design);
        });
      },
      exportHtml() {
        this.$refs.emailEditor.editor.exportHtml((data) => {
          console.log('exportHtml', data);
        });
      },
    },
  };
</script>

👉 See the full Vue Email Builder Issues and Fixes Guide for detailed solutions.

Quick comparison: Unlayer troubleshooting by framework

When to Contact Unlayer Support?

Most issues can be solved through the Unlayer Docs and troubleshooting resources. But if you’ve already tried those and are still running into problems, it’s time to reach out to the official Unlayer customer support team.

You should contact support if:

• The issue persists after following the documented fixes.

• You’re experiencing problems unique to your production environment.

• You’re running into urgent account, billing, or plan-related problems.

• You need help with enterprise features, integrations, or security concerns.

Support options available:

Unlayer provides multiple ways to get in touch depending on your needs:

• Technical & Billing Support → If you’re facing editor bugs, billing problems, or account access issues, you can connect with their technical team.

• Sales & Pricing Inquiries → For questions about upgrading plans, enterprise features, or custom solutions.

• Partnerships & Media → For collaboration opportunities, press coverage, or media requests.

• General Inquiries → For anything that doesn’t fit the above categories.

👉 You can explore all these options on the official Unlayer Contact Page.

To Wrap It All Up

Troubleshooting doesn’t have to be a guessing game. Bookmark this page as your go-to Unlayer support guide so you’ll always know where to start when issues come up. 

And remember, if you ever need more personalized assistance, Unlayer customer support is just a click away.

Frequently Asked Questions (FAQ)

1. Is there a free version of Unlayer?

Unlayer does offer a free tier, but it comes with limitations such as restricted access to premium features and APIs (like the Export Cloud API). For full functionality, including enterprise-grade features, you’ll need a paid plan.

2. Can Unlayer handle large-scale email or page design projects?

Yes. Many SaaS platforms and enterprises use Unlayer to power design editors for thousands of users. It’s built to scale, with features like built-in tools, custom tools, advanced customization options, team collaboration, and API-based export workflows.

3. What’s the difference between the Unlayer editor and the Unlayer API?

• Unlayer Editor (Embeddable SDK): A drag-and-drop editor you embed directly in your app.

• Unlayer API: A service layer to connect the editor with your own storage or backend systems for loading, saving, and exporting designs, managing templates, or rendering emails at scale.

Related: APIs and SDKs: What’s the Difference & When to Use Them?

4. Can I customize the Unlayer editor to match my brand?

Yes. With advanced customization options, you can change themes, appearance, editor behavior, content settings, fonts, colors, and UI styling so the editor feels native. 

You can also add/remove tools, define default templates, and even integrate your own custom tools/blocks.

5. How secure is Unlayer for production apps?

Unlayer uses Identity Verification with security signatures to authenticate sessions, and it’s SOC 2 Type II certified and GDPR compliant. 

That means you can safely use it in enterprise apps that require high standards for data privacy and security.

6. Does Unlayer work offline?

No. Unlayer is a cloud-based editor and requires an internet connection to load its assets, tools, and templates. If you’re testing locally, ensure your network allows external requests to Unlayer’s servers.