A swipe file with five examples is a tweet thread. A swipe file with fifty examples is a resource. The number is the value proposition. So is the source: 'cold opens from Stripe, Linear, and Notion' converts harder than 'cold opens from various companies.' Most share cards for swipe files surface neither. They show a stock OG image with the title and the reader has to click through to learn whether the file is worth their time.

SleekPixel surfaces the count and the source on the card itself. The repeater of examples on the post drives the count automatically. A 'sources' field on the post drives a credibility line near the title. The template renders a Twitter card sized 1200x675, with the title leading, the count in a corner, and the source line subtle but readable. On save, the card renders and og:image updates.

The right reader sees the count and the sources and clicks because the file is exactly what they wanted. The wrong reader keeps scrolling, which saves both sides time. The post drives the card. The sources drive the credibility. The count drives the click.

Swipe files have always sold on two numbers: how many examples and who they come from. Curators know this and put both in the headline of the landing page. The share card, where the headline is on stage in the feed, often loses both signals to whatever stock OG image WordPress assigns.

SleekPixel fixes that. The count comes from the actual length of the swipes repeater, so it stays correct as the file grows. The source line comes from a curated field or a unique-source rollup, so credibility is structural rather than something a designer has to remember to update.

Readers in the feed see both signals before they click and self-select cleanly. Curators stop losing right-fit readers to title-only previews. The swipe file becomes a discoverable product instead of a buried URL, because the share surface honestly reflects what the file actually is.