Conecta Isotope, una biblioteca de diseño JavaScript de Metafizzy, con Webflow para crear cuadrículas masonry animadas con filtrado, ordenación y transiciones CSS del lado del cliente en las Listas de colección del CMS.
Isotope turns any Collection List into an animated, filterable masonry grid. Connect it to the CMS, and visitors can click filters, watch items reflow with CSS transitions, and sort results without a page reload.
Native CMS filters only work at design time, so interactive client-side filtering needs custom code. If you build portfolio sites, product catalogs, resource libraries, or filterable directories, Isotope is worth a look.
How to integrate Isotope with Webflow
What is Isotope?Isotope is a client-side JavaScript layout library by Metafizzy with animated filtering, sorting, and grid-layout capabilities for web interfaces. It operates on a container element and its direct child items, repositioning them using CSS transforms and transitions entirely in the browser. Isotope includes layout modes such as masonry, fitRows, and vertical, with modes like packery available through separate installation, along with multi-criteria AND/OR/NOT filter logic and custom sort functions.
Reach for Isotope when you want visitors to interact with a grid of CMS items, filtering by multiple categories and watching items animate into place. On a portfolio page, clicking "Branding" can hide non-matching projects while the remaining cards reflow into a gap-free masonry layout. The CMS handles content and responsive design while Isotope handles the client-side layout behavior.
You can connect Isotope to your site in 2 ways:
Custom code embeds handle filtering, sorting, and masonry layouts by loading Isotope via CDN and initializing it with JavaScript in site or page settings.
The Data API with Isotope lets you control CMS content delivery for headless or SPA-based setups, but requires server-side development.
Most implementations use the custom code embed approach. Choose the API path when you need to fetch CMS content programmatically rather than rely on rendered Collection Lists.
Add Isotope with custom code
Isotope has no Marketplace app because it's a client-side JavaScript library with no server-side component. Add animated masonry grids, multi-criteria filtering, and custom sorting to any page with a Collection List through CDN script tags and initialization code added via custom code in head and body tags or Code Embed elements. You need a paid site plan because custom code isn't available on the free plan. Commercial client projects also require a paid Isotope license starting at $25.
To set up Isotope on a CMS-driven page:
Open Page Settings for the target page, scroll to the Before
tag section, and add CDN script tags for imagesLoaded and Isotope:
Add a Div Block with the class portfolio-grid as the Isotope container. Place a Collection List inside it. Give each Collection Item an additional class like portfolio-item to use as the itemSelector. Don't rely on the auto-generated w-dyn-item class.
Add an Option or Multi-reference field to your CMS Collection for categories, for example, web, print, branding. Output those category values as CSS classes on each portfolio-item so Isotope can match selector-based filters like .web and .print.
Add filter buttons above the grid. Create a Div Block with class filter-button-group and add Button elements inside it. On each button, add a data-filter custom attribute with the matching CSS selector, for example, .web or .print. Use an empty string for the "All" button.
Below the CDN script tags in Before , add the initialization script:
<script>
document.addEventListener('DOMContentLoaded', function() {
var grid = document.querySelector('.portfolio-grid');
var iso;
imagesLoaded(grid, function() {
iso = new Isotope(grid, {
itemSelector: '.portfolio-item',
layoutMode: 'masonry',
percentPosition: true,
masonry: {
columnWidth: '.portfolio-item'
}
});
});
var filterGroup = document.querySelector('.filter-button-group');
if (filterGroup) {
filterGroup.addEventListener('click', function(e) {
if (!e.target.matches('button')) return;
var filterValue = e.target.getAttribute('data-filter');
iso.arrange({ filter: filterValue });
filterGroup.querySelectorAll('button').forEach(function(b) {
b.classList.remove('is-checked');
});
e.target.classList.add('is-checked');
});
}
});
</script>
Publish the site and test on the live URL or staging preview. Isotope doesn't execute in the Designer canvas.
With this setup, you can use:
Animated masonry, fitRows, or vertical grid layouts with CSS transitions
Multi-criteria filtering using AND (.web.branding), OR (.web, .print), and NOT (:not(.print)) logic
Custom sorting by data attributes, text content, or parsed numeric values
Responsive percentage-based widths with percentPosition: true and a .grid-sizer element
These options cover most interactive CMS-driven grid layouts you'll build.
Collection Lists are limited to 100 items per list. If your collection exceeds 100 items, you need a de-pagination tool like Finsweet CMS Load to merge paginated output into a single DOM list before Isotope initializes. Keep in mind that rendering hundreds of items simultaneously affects page performance.
Handle images and prevent overlapping items
Images lazy-load by default. Isotope calculates item positions at initialization, and if images haven't loaded yet, the calculated heights are wrong. Items overlap. The imagesLoaded library you added in step 1 solves this.
To prevent overlap on image-heavy grids:
Wrap the Isotope initialization inside an imagesLoaded callback as shown in step 5 above.
For grids where you want items to appear as images load progressively, initialize Isotope first and then call layout as each image finishes:
var iso = new Isotope(grid, { itemSelector: '.portfolio-item' });
imagesLoaded(grid).on('progress', function() {
iso.layout();
});
If your grid layout corrects itself when you manually resize the browser window, you have an imagesLoaded issue. The GitHub issue github.com/metafizzy/isotope/issues/1670 documents this diagnostic symptom.
Add sorting controls
Isotope can sort items by any data attribute, text content, or computed value stored on the Collection Item elements.
To add sorting to a CMS-backed grid:
Store sortable values as data attributes on your Collection Items. For example, add data-date bound to a CMS Date field and data-category bound to a CMS Option field.
Define getSortData in your Isotope options to tell the library how to extract sort values:
iso = new Isotope(grid, {
itemSelector: '.portfolio-item',
getSortData: {
name: '.project-name',
date: '[data-date]',
price: '.price parseFloat',
category: '[data-category]'
}
});
Add sort buttons with data-sort-by attributes matching your getSortData keys. Attach a click handler that calls iso.arrange({ sortBy: value }):
You can combine sorting with filtering in a single iso.arrange() call by passing both filter and sortBy options together.
Prevent FOUC and CSS conflicts
Visitors may see unstyled items stacked in normal document flow for a brief moment before Isotope applies absolute positioning. Interactions (IX2) can also conflict with Isotope because both systems manipulate CSS transform and opacity properties.
To prevent flash of unstyled content (FOUC):
Add a CSS rule to hide the grid initially: .portfolio-grid { opacity: 0; transition: opacity 0.3s; }
Add a reveal class after Isotope initializes:
imagesLoaded(grid, function() {
iso = new Isotope(grid, { /* options */ });
grid.classList.add('isotope-ready');
});
Add the reveal rule: .portfolio-grid.isotope-ready { opacity: 1; }
To avoid CSS transition conflicts, never set transition: all on grid items. Isotope controls transform and opacity internally. Only transition non-positional properties:
Remove any IX2 interactions from elements inside the Isotope grid. Applying IX2 entrance animations or scroll effects to Isotope-managed elements causes values to overwrite each other. The Isotope FAQ on CSS conflicts covers this in detail.
Build with the Data API and Isotope
For headless setups or single-page applications that need to fetch CMS content programmatically, use the Data API v2 to pull collection items and render them into DOM elements that Isotope manages. This approach requires server-side development and fits when you aren't using the native CMS rendering.
The relevant APIs include:
The CMS Items endpoint returns paginated collection data as JSON, up to 100 items per request
Webhooks fire server-side HTTP POST notifications on events like collection_item_created and collection_item_changed
Isotope's client-side JavaScript API provides methods like iso.appended() and iso.arrange() to update the grid after new items load
These two APIs operate in different environments. Webhooks and REST endpoints run server-side. Isotope methods run in the browser. You'll need a server-side intermediary to bridge the two.
Fetch CMS items and render an Isotope grid
Use this pattern when you need to build a filterable grid outside of the native CMS rendering, for example in a custom frontend that consumes the CMS as a headless source.
To implement a headless Isotope grid:
Fetch collection items from GET /v2/collections/{collection_id}/items with pagination (limit=100&offset=0). Authenticate with a Bearer token.
Render each item as a DOM element with CSS classes or data-* attributes matching your filter and sort configuration.
Initialize Isotope on the container after all items are in the DOM:
var iso = new Isotope('.grid', {
itemSelector: '.grid-item',
layoutMode: 'masonry',
getSortData: {
name: '.name',
category: '[data-category]'
}
});
For subsequent pages of content, fetch the next batch, render the elements, and call iso.appended(newElements) to add them to the layout.
Webhooks like collection_item_created and collection_item_changed can trigger your server to rebuild or update the rendered grid. The webhook events reference documents all available trigger types.
What can you build with the Isotope Webflow integration?
Adding Isotope to your site lets you create interactive, animated grid layouts driven by CMS data without building a custom frontend from scratch.
Filterable portfolio galleries: Build a design agency portfolio where visitors filter projects by service type, industry, and project scale. Items animate into a masonry layout with variable-height thumbnails filling gaps automatically.
Multi-criteria product catalogs: Create an e-commerce product grid where shoppers filter by category, price range, and availability simultaneously using AND/OR logic. Items reflow with transitions as filters change.
Sortable resource libraries: Set up a knowledge base page where visitors filter articles by topic and format, sort by publication date or difficulty level, and see results rearrange in real time without a page reload.
Interactive team directories: Build a people page for a professional services firm where visitors filter team members by department and office location, with alphabetical sort toggling between ascending and descending order.
If you need more control over CMS content delivery for large collections or headless setups, the API integration path handles those cases directly.
Preguntas frecuentes
Sí. Todo proyecto comercial en Webflow requiere una licencia de pago de Isotope. El plan Developer cuesta 25 $ para un desarrollador e incluye Isotope v3. La excepción de código abierto GPLv3 solo es válida si tu aplicación completa se publica bajo una licencia compatible con GPL. Si vas a distribuir una plantilla o un clonable de Webflow que incluya Isotope, necesitarás una licencia OEM independiente de Metafizzy.
Los elementos se superponen cuando las imágenes o las fuentes web se cargan después de que Isotope calcula las posiciones. Webflow carga las imágenes de forma diferida (lazy-load) por defecto, lo que provoca este problema en casi todas las cuadrículas que contienen imágenes. Envuelve la inicialización de Isotope dentro de una devolución de llamada (callback) como se describe en la documentación de diseño de Isotope. Si los elementos se corrigen al cambiar el tamaño de la ventana del navegador, el problema está confirmado.imagesLoadedimagesLoaded
Una lista de colección renderiza un máximo de 100 elementos. Isotope solo puede filtrar elementos que existen en el DOM, por lo que los elementos que superan ese límite son invisibles para él. Para solucionar esto, utiliza Finsweet CMS Load para eliminar la paginación de la lista de colección y convertirla en una sola lista en el DOM antes de que Isotope se inicialice. También puedes colocar hasta 20 listas de colección en una página con filtros de rango y combinarlas con JavaScript. La estructura de la colección debe planificarse antes de empezar a construir.
Isotope funciona en el sitio publicado o en la URL de vista previa, no en el lienzo de Webflow. Construye la estructura de tu cuadrícula y las clases en Webflow, y luego verifica el filtrado, la ordenación y el comportamiento del diseño en el dominio en vivo.
Apuesta por Isotope si buscas transiciones animadas con elementos que se mueven y reorganizan ante tus ojos, o cuadrículas estilo masonry/packery. Finsweet Attributes es una alternativa más sencilla cuando solo necesitas filtros interactivos sin reordenaciones animadas, ya que no requiere más JavaScript que pegar una sola etiqueta de script. Finsweet Attributes no admite el modo masonry, así que Isotope sigue siendo el rey cuando necesitas combinar cuadrículas masonry y filtros en la misma página.
Isotope añade filtrado animado, ordenación y diseños masonry a las cuadrículas del CMS de Webflow mediante etiquetas de script CDN y código personalizado. Los visitantes pueden filtrar y ordenar elementos con transiciones CSS sin necesidad de recargar la página.
Esta página de integración se ofrece únicamente con fines informativos y de conveniencia.
Other Biblioteca de plugins e integraciones integrations
Other Biblioteca de plugins e integraciones integrations
Hacks de Finsweet para Webflow
Añade Finsweet Hacks a Webflow con código personalizado: mensajes de éxito en formularios con nombres, URLs de anclaje limpias, una calculadora de precios con casillas de verificación y cuándo usar Attributes.
Conecta Drupal con Webflow para ofrecer contenido gestionado a través de un frontend visual mediante sincronización por API, herramientas de automatización o integraciones del lado del cliente.
Conecta Finsweet Components, una aplicación nativa de Webflow, para añadir controles deslizantes, marquesinas, feeds de redes sociales, favoritos y pestañas automáticas con JavaScript directamente en el Diseñador de Webflow, sin necesidad de código personalizado.
Añade y elimina clases CSS en elementos de Webflow al hacer clic, pasar el cursor, desplazarse o cargar la página mediante un script generado por el Visual Builder de Finsweet.
Conecta Pixie con Webflow para automatizar la optimización de imágenes del CMS, reducir el tamaño de los archivos y acelerar los tiempos de carga de tus páginas.
Añade un menú de restaurante de One2 Menu a una página de Webflow mediante un fragmento de código, para menús con código QR y cambios de precio que se publican al instante sin necesidad de volver a publicar la página.
Conecta Flowstar Tabs, un creador de pestañas sin código, con Webflow para organizar los detalles de tus productos, incluidas las especificaciones, en secciones de información personalizables con pestañas.
Prueba Webflow todo el tiempo que quieras con nuestro plan Starter gratuito. Compra un plan de sitio de pago para publicar, alojar y desbloquear funciones adicionales.