How viratvasu0/vidflow works
VidFlow accepts a YouTube URL, fetches video metadata and available stream formats, then lets the user select and open a stream URL. A separate download API route uses ytdl-core to retrieve and return a stream, but the sampled UI does not call that route. Metadata lookup tries public Invidious instances and falls back to YouTube oEmbed; the excerpts do not establish how Invidious stream URLs are served. The graph reflects the sampled routes and UI only.
Main entry points: page.js URL and format UI · info/route.js Metadata and formats · layout.js App shell · download/route.js Download stream route
Components 8
User experience
- URL and format UI
app/page.js - App shell
app/layout.js
Video discovery
- Metadata and formats
app/api/info/route.js - Invidious instances
- YouTube APIs
Stream delivery
- Download stream route
app/api/download/route.js - Selected media URL
Other components
- Visitor
Connections 7
- Visitor → URL and format UI: submits URL
app/page.js - App shell → URL and format UI: renders
app/layout.js - URL and format UI → Metadata and formats: requests metadata
app/page.js - Metadata and formats → Invidious instances: tries instances
app/api/info/route.js - Metadata and formats → YouTube APIs: falls back to oEmbed
app/api/info/route.js - URL and format UI → Selected media URL: opens selected URL
app/page.js - Download stream route → YouTube APIs: retrieves stream
app/api/download/route.js