Social Feed for TYPO3

Social media feeds on the website look great but regularly break through API changes

Marketing teams want to display Instagram posts, Facebook updates or Twitter/X tweets on the corporate website. The reasoning is understandable: fresh content without editorial effort, social proof through real posts, visual enhancement through image material. The reality looks different. Meta, Twitter/X and TikTok regularly change their APIs, restrict access rights or shut down free endpoints entirely. Twitter/X eliminated free API access in 2023, charging at least 100 USD/month for read access since then. The Instagram Basic Display API was replaced by the Instagram Graph API in 2024. Anyone operating a social feed integration must track these changes or the feed stays empty.

pxa_social_feed (developed by Pixelant) is the best-known TYPO3 extension for social media feeds. It supports Instagram, Facebook and Twitter/X, stores feed data locally (cached) and renders it as a TYPO3 content element. The extension is open source and maintained by the community.

Typical use cases

Corporate websites with Instagram feed on the homepage. A company posts 3 to 5 times per week on Instagram and wants to display the latest 6 to 12 posts as an image gallery on the homepage. pxa_social_feed fetches posts via cron job (e.g. every 30 minutes), stores images, captions and links locally and renders them in a configurable grid. The advantage over an embed (iframe): no external requests on page load, no tracking pixels, faster loading time.

Event pages with live feed. Conferences, trade shows or company celebrations use a hashtag (e.g. #GosignSummit2026). The feed shows all public posts with this hashtag in real time (or near-real-time with 5-minute caching). Moderation happens in the TYPO3 backend: individual posts can be hidden before they appear on the website.

Employer branding pages. HR departments show insights from daily work life on the careers page, posted by employees on Instagram or LinkedIn. The integration collects posts from one or more accounts and curates them editorially. Limitation: LinkedIn offers no open API for feed integration, so automation is restricted to Instagram and Facebook.

Technical architecture

pxa_social_feed uses the APIs of the respective platforms: Instagram Graph API (via a Facebook app token), Facebook Graph API and Twitter/X API v2. Each platform requires its own authentication: Facebook and Instagram need a Long-Lived User Token (valid 60 days, must be renewed regularly), Twitter/X needs a Bearer Token (Application-only Auth).

The extension stores feed data in a local TYPO3 table (tx_pxasocialfeed_domain_model_feed). Images are downloaded and stored as FAL references. On page load, only local data is rendered - no external API calls. A scheduler task fetches new posts and removes old ones (configurable: keep last 50 posts, delete older ones).

Output uses Fluid templates configured via TypoScript. Standard layouts: grid (3-4 columns), masonry, slider (via custom JavaScript integration). The HTML/CSS can be fully customized without modifying extension code.

For GDPR compliance, the local cache is crucial: because images and texts reside on the company’s own server, no data is transmitted to Meta or Twitter/X on page load. No tracking pixel, no cookie consent needed for the feed itself. Exception: if the “View original post” link is included, a redirect occurs on click.

Common problems and solutions

Instagram token expires, feed stays empty. The Long-Lived Token has a lifespan of 60 days. If nobody renews it, the import stops. Solution: set up a cronjob that automatically extends the token via API call (the endpoint GET /oauth/access_token?grant_type=fb_exchange_token returns a new token). pxa_social_feed offers a token refresh function in the backend since version 4.x.

Twitter/X feed stops working after API change. Since 2023, the Twitter/X API is paid. The Basic tier (100 USD/month) allows reading 10,000 tweets/month. For most corporate websites that suffices, but the cost-benefit equation must work. Solution: check whether the Twitter/X feed actually drives traffic or engagement. If not, remove the channel and keep only Instagram/Facebook.

Images not loading or appearing pixelated. The Instagram Graph API delivers images in various sizes. pxa_social_feed stores the version delivered by the API by default. Solution: set image size to “original” in the extension configuration and generate responsive variants via <f:image> in the Fluid template.

Migration and version compatibility

pxa_social_feed supports TYPO3 v11 and v12. Compatibility with TYPO3 v13 is in community development (as of April 2026) but not officially released. For projects on TYPO3 v13, there are two options: wait for the official update or build a custom feed integration as middleware that runs independently of the TYPO3 version.

Fundamentally, Gosign recommends thinking of social feed integrations as decoupled components: a microservice or Cloudflare Worker fetches the feeds, stores them as JSON, TYPO3 reads the JSON and renders it. This eliminates the dependency on a TYPO3 extension and any API change is fixed in one place, independent of the CMS.

When deciding which social media channels to embed on the website, Gosign recommends a data-driven evaluation: which channel actually drives engagement? Instagram feeds with high-quality images work well on corporate websites, Twitter/X feeds are not worth the effort for most companies since API costs were introduced, and Facebook feeds have declining relevance as organic reach has been falling for years. LinkedIn would be the most relevant channel for B2B companies but offers no open feed API. The pragmatic solution: embed Instagram as the primary channel, manually curate LinkedIn posts as TYPO3 content, and skip Twitter/X unless the channel is business-critical.

The total effort for a social feed integration (Instagram, cached, GDPR-compliant, with backend moderation) is 2 to 5 development days, depending on whether pxa_social_feed is sufficient or a custom solution is needed.