Platforms

Webflow Google reviews integration: what the 940 px container does

3 August 2026 · JustReview

Webflow takes a Google reviews snippet in three different places, and all three publish the same markup: an HTML Embed element on the canvas, the custom code fields in Page settings, or the same fields in Site settings. The part nobody tells you is what happens after that. A Webflow site is a grid with fixed breakpoints, a reviews slider measures the browser window, and those two rulers do not agree. Below are the numbers from a live Webflow page, measured today, plus the three settings that make the mismatch disappear.

Where Webflow will take the code

The character allowance is worth a moment, because it is the reason a lot of embed code gets rejected in Webflow, and it used to be five times tighter. Webflow states plainly that code in a Code Embed element cannot exceed 50,000 characters, and that the Head and Footer fields in Site settings and the equivalents in Page settings hold 50,000 characters each.

How much of that allowance a reviews widget uses

Every number below comes from the snippet builder inside the JustReview panel, run on 3 August 2026 with each widget screen in its default state. Two figures per widget: the snippet as the panel writes it for an account with all 38 review sources ticked, and the same snippet for a fresh account with only Google connected. Both include the stylesheet link, the library tag and the container div, so it is the complete paste.

The two library tags on their own, the stylesheet and the script, are 147 characters. Everything else is the settings you chose in the panel, written out as readable JavaScript rather than minified, which is why the number grows with the list of connected sources: each one costs about thirteen characters. Even the heaviest of these, at 2,129 characters, leaves room for twenty-two more copies in the same embed. If you are hunting for a way around a Webflow character limit, a review widget is not what put you over it.

What the default container does to a slider

This is the part that surprises people. The runs below are from a published Webflow page served with Webflow’s own stylesheet and runtime, jQuery 3.5.1 and webflow.js loaded exactly as Webflow publishes them, with the snippet inside a w-embed w-script wrapper, which is what the Designer produces from an Embed element. The only variable is the width of the browser window.

Read the container column first. Webflow’s container is 940 px wide on desktop, drops to 728 px at 991 px of window width, and goes fluid below 479 px. That is the whole responsive story on Webflow’s side, and it is the same on every site built with the default grid.

Now read the card column. It does not shrink smoothly. It jumps up at 1023 px, falls again at 991 px, drifts down to its narrowest point at 600 px, then jumps to 489 px one pixel later. The widest cards on the entire scale, 489 px, appear on a 599 px window, which is a large phone in landscape. The narrowest, 230 px, appear at 600 px, one pixel apart.

The 32 pixels where the two rulers disagree

The slider counts how many cards fit by looking at the browser window, not at the box it was given. We measured its two thresholds precisely: three cards down to two between 1024 px and 1023 px, and two down to one between 600 px and 599 px. Webflow’s thresholds are 991 px, 767 px and 479 px. Nothing lines up.

The visible consequence lives in the gap between 1023 px and 992 px. There, Webflow still gives the block its full 940 px, because the tablet breakpoint has not fired yet, while the slider has already decided this is a smaller screen and switched to two cards. The result is a 940 px block holding two 400 px cards where the same block held three 257 px cards thirty-two pixels earlier. Nothing is broken, nothing logs an error, and every visitor on a 13-inch laptop with a slightly narrow window sees a different layout than the one you approved on your monitor.

The second gap runs from 599 px down to 480 px: one card per screen while Webflow still treats the page as mobile landscape. That one is harmless, because one card on a phone is the right answer anyway.

Columns are where it actually breaks

Dropping the Embed into a Webflow column is the placement worth avoiding. In a w-col-4 column inside the default container, on a 1440 px screen, the column measured 300 px of usable width, and the slider still tried to fit three cards into it: 80 px each. At 991 px the same column shrinks to 229 px and the content starts to overflow its own box by 26 px.

The mechanism is the one we measured in a different builder, where a slider that starts inside a hidden Elementor tab comes out with one full-width card: a component that has to know its own width behaves badly when the width it is told about is not the width it has. In Webflow the container never hides, so the failure is quieter and easier to miss. It just looks like small reviews.

Three settings that remove all of it

Give the slider a full-width section rather than the default container when you want large cards. Measured on the same page at 1440 px, a full-width section produced 423 px cards against 257 px in the container, and the block was the same height either way. This is one checkbox in Webflow, on the section rather than on the embed.

Set the visible slides count to match the placement instead of leaving it at three. Three is right for a full-width section and wrong for anything narrower than the container. Two is the safe choice for a 940 px container, and it removes the jump at 1023 px entirely, because the slider is already showing two.

Reserve the height. Every layout in the table above landed between 754 px and 784 px, a 30 px spread across every screen size we tested, so a section with a 780 px minimum height will not shift the page underneath it while the reviews load. If you need a shorter block, turn off the header or the button in the widget settings before you start fighting it with CSS.

And check on the published site or in preview, not on the canvas. An Embed element shows a placeholder while you design, which is normal and not a sign that anything is wrong.

Where the reviews themselves come from

None of the above matters if the reviews are stuck in a place you cannot export. That is the actual reason to connect a review account rather than paste static quotes into Webflow: the Google profile keeps collecting reviews, the widget keeps showing the current ones, and the Webflow page never has to be edited again. Connect Google once and the same snippet keeps working, whether your business has one location or twenty. The same account also pulls from Facebook, Booksy, Allegro, G2, Capterra and thirty more sources, so a Webflow page can show one merged wall instead of four separate widgets from four vendors, which is also why our snippets grow by thirteen characters per source rather than by a whole new script tag.

Our own numbers on this page are the honest version: the library and the stylesheet are two requests, the reviews arrive in a single API call, and on a Webflow page with jQuery and webflow.js already running we recorded zero console errors across every window size in the table. Details on the embed itself, including the settings that produced these measurements, live on the widget page, and the universal embed instructions cover Webflow’s Embed element step by step.

The reservations, since every tool has them. The widget renders on the client, so the reviews are not in the HTML that Webflow publishes, and a crawler that does not run JavaScript will not see the review text. If that matters for a specific page, use the aggregate rating option, which writes structured data rather than relying on the rendered cards. Free accounts show the JustReview logo under the reviews; removing it is a paid setting, and you can see exactly which plan carries it on the pricing page.

If your Webflow site is waiting on this, the shortest path is to create an account, connect Google, copy the snippet the panel writes for you, and drop it into a full-width section with the visible slides set to two or three. That is roughly ten minutes, most of which is Google’s authorisation screen, and 2,129 characters of the 50,000 Webflow gives you.