How do I embed Spotify tracks, Instagram posts, and other content in my posts?

VeloCMS embeds Spotify, Instagram, Pinterest, LinkedIn, CodePen, SoundCloud, and Calendly automatically — paste the content's URL on its own empty line in the TipTap editor and the platform-branded player or card renders in your post. There is no Twitter/X provider today; a pasted tweet URL stays a plain link.

Which platforms are supported out of the box?

The auto-embed engine recognizes URLs from Spotify (tracks, albums, playlists, episodes, shows, and artists), Instagram (posts, reels, and IGTV — public content only), Pinterest (pins), LinkedIn (feed post updates), CodePen (public pens), SoundCloud (public tracks), Calendly (scheduling pages), and YouTube and Vimeo (covered in a separate guide). For a provider not on this list, use the Embed command and paste the URL — an unrecognized host falls back to a plain link card rather than an iframe.

How do I embed a Spotify track or playlist?

Open the track, album, or playlist in Spotify's web player (open.spotify.com), copy the URL from your browser's address bar, and paste it on a new empty line in the VeloCMS editor. The Spotify player widget appears — it shows album art, the track title, and plays a preview without leaving your post. If you're embedding a full playlist, readers can scroll through the tracks inside the embedded player. Full tracks require a free or paid Spotify account on the reader's side; VeloCMS doesn't gate this.

How do I embed an Instagram post or a Pinterest pin?

Grab the post's share link from Instagram (the ••• menu → 'Copy Link') or the pin's URL from Pinterest, and paste it on its own empty line in the editor. Both render via the platform's own embed script rather than an iframe — Instagram's embed.js and Pinterest's pinit.js — so nothing loads until your reader's browser processes the block. If the source post goes private after you embed it, the embed breaks and shows a fallback.

What about performance — do embeds slow down my page?

Third-party embeds always carry a performance cost because they require loading JavaScript and CSS from external domains. VeloCMS mitigates this with lazy loading — embedded players and scripts only initialize when they scroll into the reader's viewport. The initial page load stays fast because the embed placeholder is just a static HTML structure with no blocking scripts. That said, pages with many social embeds will still load slower than text-only posts.