About this project

Syncrify is presented as an all-in-one, self-hosted media orchestrator and format converter. It combines yt-dlp-based source ingestion with ffmpeg transcoding behind a browser-first dashboard, aiming to remove format fragmentation for personal archives and offline playback. Core capabilities described in the README: - Universal ingestion: claims support for YouTube, Spotify, Apple Music, Deezer, SoundCloud, Vimeo, Dailymotion, Bandcamp and many smaller platforms through a yt-dlp backend, including playlist and channel detection and pre-flight URL validation. - Format transformation: preset profiles for MP3, M4A, FLAC, Opus, MP4, MKV and WebM, plus custom ffmpeg/yt-dlp flag injection and subtitle extraction, embedding or hardcoding. - Web dashboard: progressive web app layout for desktop, tablet and mobile, with real-time progress, error logs, estimated completion times, dark/light themes and a six-language interface (English, Spanish, German, Japanese, French, Portuguese). - Desktop companion: a tray application for Windows, macOS and Linux with clipboard URL capture and a background service mode. - Organization: template-based naming such as {playlist_title}/{track_number} - {title}.{ext}, automatic folder creation and duplicate detection by source URL and output path. - Automation: recurring daily/weekly queues, email notifications on completion or failure, and an API endpoint for external triggers such as Home Assistant, IFTTT or custom scripts. Architecture is described as three layers: a Vue.js presentation layer, a Node.js orchestrator handling sessions, queue persistence, rate limiting and health monitoring, and a Python execution layer containing yt-dlp, static ffmpeg builds and metadata extractors for Spotify and Apple Music. All layers are said to run in a single container image for x86 or ARM deployment. Configuration is exposed through a syncrify.conf file with over 120 parameters, including custom ffmpeg presets, webhook integration for Discord, Slack or custom endpoints, post-processing shell hooks (for example S3 upload, BPM-based renaming or transcription) and environment variable overrides for containers. Privacy claims include local-only processing, a local authentication gate, optional TLS for reverse proxies, and no telemetry or analytics. The README also lists contribution areas, a quarterly roadmap through 2026, an MIT license, and a disclaimer that the tool is intended for personal, archival and educational use, with users responsible for platform terms of service compliance. Note: the README contains promotional download buttons and roadmap items; these are author claims rather than independently verified features.