Issue #3427💬 AnsweredOpened May 1, 2021by akmittal1 reactions

Add lazy loading support for images

快速解答by artf1

Thanks @akmittal loading is actually really cool and useful but, for now, I'd like to avoid extending core components (this might lead to unexpected behavior if someone creates a new component by extending the image). For anyone who wants to make use of loading attribute can easily extend the image component in this w...

Read full answer below ↓

Question

What are you trying to add to GrapesJS? Lazily loading support for images.

Describe your feature request detailed Latest Browsers support lazy loading of images using the loading attribute. <img src="myimg.png" loading="lazy">. There are two possible values eager and lazy. If a loading attribute is not provided images loading is eager. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img

Is there an alternative at the latest version?

  • Yes (describe the alternative)
  • No

Is this related to an issue?

  • Yes (Give a link to the issue)
  • No

Answers (2)

artfMay 7, 2021

Thanks @akmittal loading is actually really cool and useful but, for now, I'd like to avoid extending core components (this might lead to unexpected behavior if someone creates a new component by extending the image). For anyone who wants to make use of loading attribute can easily extend the image component in this way

editor.DomComponents.addType('image', {
  model: {
    defaults: () => ({
      traits: [
        'alt',
        {
          type: 'select',
          name: 'loading',
          label: 'Loading',
          default: 'eager',
          options: [
            { id: 'lazy', name: 'Lazy' },
            { id: 'eager', name: 'Eager' }
          ]
        }
      ],
    }),
  },
});
ClaudeCodeMay 17, 2026

Thanks for reporting this, @akmittal.

Great suggestion about FEAT: Add lazy loading support for images! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior.

Using the event system:

editor.on('component:update', (component) => {
  // your logic here
});

Alternative approaches:

  • Listen to selector:add for CSS selector changes
  • Use selector:custom for custom rules
  • Tap into the change:* events for fine-grained tracking
  • Build a plugin that extends the editor with this capability

Making it official: If this feature would benefit many users, consider opening a formal Feature Request on the GrapesJS repo with:

  • A detailed use case
  • Code example showing the desired behavior
  • Why this matters for your workflow

The core team is receptive to well-motivated feature requests backed by real use cases.

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.