Recent track list
Display the last 10–20 songs or another practical history depth supported by the source.
Turn compatible recent-track metadata into a clean, responsive list that can be embedded on a station website or integrated into a custom radio player.
Display the last 10–20 songs or another practical history depth supported by the source.
Use compatible station history endpoints rather than manually updating song lists.
Match the history card to the station website and player branding.
Keep the component lightweight and refresh only the data that changes.
Place the widget on a homepage, player page or dedicated recently-played section.
Integrate with AzuraCast or other platforms that expose usable song-history data.
Listeners often arrive after hearing part of a song and want to know what it was. A radio song history widget solves that problem by showing the most recent tracks in order. It also gives music-focused stations more useful content on the website and can encourage visitors to stay on the page longer.
AzuraCast can expose recent song information through its API, making it a strong source for a recently-played component. Other radio platforms may expose history in different formats. The widget should be built around the actual station data rather than assuming a fixed API structure.
The history should look like part of the station rather than a third-party afterthought. Colours, spacing, artwork treatment and typography can match the main website. On mobile screens the widget should remain readable without requiring horizontal scrolling.
Song history does not need to be requested every second. A sensible refresh interval can detect track changes while reducing unnecessary calls. Caching can also protect the station API and help the widget remain stable during brief upstream problems.
The strongest listener experience combines a current-song panel with recent tracks. The current track answers what is playing now, while the history lets visitors identify songs they heard earlier. Both can use the same underlying station metadata integration when the API supports it.
Add current artist and title above the recent-track list.
Explore metadata →Combine playback and song data in one branded component.
Explore player →Use a radio platform with rich structured station APIs.
Explore AzuraCast →Build the widget into a complete station website.
Explore websites →A typical design shows around 10–20 recent tracks, but the practical limit depends on the source API and page layout.
Yes. The widget can refresh station history at a sensible interval without requiring the visitor to reload the page.
Yes, if suitable artwork is supplied by the metadata source or another approved lookup workflow.
Yes. AzuraCast is well suited to song-history integrations because it exposes structured station data.
Yes. The widget can be styled to match the station's existing brand and player.
Send your station API or panel details and the website where the history should appear.