I’m using the Instagram Feed component, and I’m having issues with images rendering on the site. I’ve followed the steps in detail to set up an Meta Developer account, add the Instagram account as a test user, generated an access code, and added that access code to the project, but my images are still being rendered incorrectly.
Site URL
URL: general-dental-ae35b5 [dot] webflow [dot] io (not allowed more than two links in this post)
Webflow Read-only link: see next post
Steps to Reproduce
You’ll be able to see this on page load. The section is at the bottom of the home page here.
Expected Behavior
Instagram images render in the correct order.
Actual Behavior
On Firefox, the images are not rendered at all, and on Chrome and Safari, they are rendered, but with a duplicated image and out of order.
The cross-browser behavior you’re seeing is actually a helpful clue. Firefox showing nothing while Chrome and Safari show duplicated and out-of-order images suggests this might be a rendering or script issue rather than your Instagram connection itself.
Your HTML structure looks correct with the fs-instagramfeed-element attributes in place. The placeholder images appearing instead of actual Instagram content, combined with different browser behavior, points us toward a few areas to check:
Can you help us gather some diagnostic info?
Browser console errors — This is the most important step:
Open your site in Firefox, press F12, click the Console tab
Do the same in Chrome
Share any red error messages you see in both browsers
Verify your Instagram token — Open the Finsweet Components dashboard and check that your Instagram access token shows as connected/active
Script version check — Verify you’re using the latest version of the Finsweet Components script in your project settings
Other scripts — Let us know if you have any other custom JavaScript running on this page that might conflict
Quick context: Finsweet Components automatically renews your Instagram tokens, so manual token expiry shouldn’t be the issue if your initial setup completed successfully. The cross-browser rendering discrepancy is what’s really standing out here — it’s not a pattern we’re seeing in standard setups, which means this may need a closer look from our team.
If these diagnostic steps don’t resolve it, we’ll escalate this to @Support-Luis or @Support-Pedro for deeper investigation. They can dig into the component behavior and check if there’s something specific about your setup that needs attention.
Let us know what you find in those console logs — that’ll tell us a lot!
