Open-source project
spotbye/SpotiFLAC avatar
spotbye/SpotiFLAC

SpotiFLAC: FLAC from third-party APIs, a UPX-packed binary, and the risk you keep

Get Spotify tracks in true FLAC from Tidal, Qobuz & Amazon Music — no account required.

11,594 stars594 forksTypeScriptMIT

At a glance

What is it?
SpotiFLAC is an MIT-licensed desktop app that resolves Spotify tracks and fetches lossless audio from Tidal, Qobuz and Amazon Music without any account, built as a Go and Wails shell with a TypeScript frontend, with the failure modes and legal weight left on the user.
Who is it for?
SpotiFLAC fits a listener who wants a local lossless copy of one track and is comfortable with an unsigned build, a rate limit keyed to their IP, and no account anywhere in the chain. It does not fit anyone who needs a library they can re-download later, who works on a machine with enforced antivirus, or who needs a guarantee that the upstream endpoints will still exist next month.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 90 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on October 19, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • spotbye/SpotiFLAC11,594 ★ · +440
Star history
Repository2026-09-222026-10-19
spotbye/SpotiFLAC11.2k11.6k

440 Stars in the last 27 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The desktop build is a Go and Wails shell with a TypeScript frontend

The repository is not a browser extension and the README never presents it as one. The top level holds main.go, app.go, wails.json, a backend/ directory, a frontend/ directory, go.mod and go.sum, and go.mod requires github.com/wailsapp/wails/v2 v2.13.0, the framework that pairs a Go binary with a system webview. That is also why the repository is tagged as TypeScript as its primary language while the module itself declares module github.com/spotbye/SpotiFLAC: the frontend is TypeScript and the shell around it is Go. The only distribution path the README offers is a Download button pointing at the latest release page, and there is no install command, no package manager entry and no documented build invocation anywhere on the page. If you expected to drop an extension into Chrome, the Android and iOS builds by @zarzet, or the Python library by @BartolomeoRusso9, those are separate community projects, and the README states plainly that related projects are maintained by the community and are not affiliated with the core SpotiFLAC desktop build.

Audio comes from third-party APIs, which is why your IP address is the weak link

The project states that the audio is fetched using third-party APIs, and it credits the services it leans on: MusicBrainz, LRCLIB, Songlink/Odesli, Songstats, hifi-api and Qobuz-DL, alongside the three stores named in its own tagline, Tidal, Qobuz and Amazon Music. Nothing in that chain is negotiated with a streaming service, which is why no account, login or subscription is needed and why the only stated requirement is an internet connection. The cost of that design is the failure mode the project itself documents. Asked why metadata fetching sometimes fails, the answer is that it usually happens because your IP address has been rate-limited, and the suggested remedies are to wait and try again later, or to use a VPN to bypass the rate limit. So the practical effect is that a shared office, campus or mobile carrier address fails in ways a single-user home connection does not, and the fix the project offers is another network path rather than a retry.

The release binary is UPX-compressed, so antivirus deletes it and the workaround is a local build

One FAQ entry is worth reading twice because it defines the install experience. Asked why Windows Defender or antivirus flags or deletes the file, the project calls it a false positive and attributes it to the executable being compressed using UPX. That is a packing tool, and packed executables match the heuristic patterns many endpoint products warn on, so the hash changes on every build and a name-based or reputation-based rule keeps firing. The stated remedy is to fork the repository and build the software yourself from source. On a managed machine with enforced antivirus, redownloading the same release artifact tends to hit the same rule again, so the fork-and-build route is the only documented path. That route is not free either: go.mod declares go 1.26, and the dependency list includes go.senan.xyz/taglib, a binding to a C++ library, so a source build needs a current Go toolchain plus a C++ toolchain rather than a single Go install.

The direct dependency list shows what writes tags, and what is absent

The direct requirements in go.mod read like a map of the pipeline, and each entry has a job. go-flac/go-flac handles the FLAC stream itself, flacpicture and flacvorbis cover the picture block and the Vorbis comment metadata, bogem/id3v2 covers ID3, Eyevinn/mp4ff covers MP4 muxing, ulikunitz/xz covers compression and pquerna/otp one-time passwords, with bbolt as an embedded store and uuid, text and image for identifiers and encoding:

code
module github.com/spotbye/SpotiFLAC

go 1.26

require (
	github.com/Eyevinn/mp4ff v0.55.0
	github.com/bogem/id3v2/v2 v2.1.4
	github.com/go-flac/flacpicture v0.3.0
	github.com/go-flac/flacvorbis v0.2.0
	github.com/go-flac/go-flac v1.0.0
	github.com/google/uuid v1.6.0
	github.com/pquerna/otp v1.5.0
	github.com/ulikunitz/xz v0.5.16
	github.com/wailsapp/wails/v2 v2.13.0
	go.etcd.io/bbolt v1.5.0
	go.senan.xyz/taglib v0.14.0
	golang.org/x/image v0.44.0
	golang.org/x/text v0.40.0
)

Notice what is missing. There is no Spotify, Tidal, Qobuz or Amazon Music client library in that list, so every byte of audio and metadata arrives as plain HTTP against the credited services. The indirect block confirms the shape, pulling in labstack/echo/v4 and gorilla/websocket for an embedded HTTP server, wailsapp/go-webview2 for the Windows webview, and tetratelabs/wazero, a WebAssembly runtime. The consequence for you is that there is no supported SDK to fall back on when an upstream endpoint changes, and no version pin on any of those APIs that the project could hold you to.

Your Spotify account is never touched, which is both the design and its limit

The FAQ is explicit about the account question: no, using the software cannot get your Spotify account suspended or banned, because the software has no connection to your Spotify account, and Spotify data is obtained through reverse engineering of the Spotify Web Player rather than through user authentication. Read that carefully, because it is the whole architecture in three sentences. There is no token, no cookie and no password to leak, so the credential-theft risk that hangs over other download tools is genuinely absent. The same design is the limit: with no authenticated session you inherit only what the web player exposes to anyone, so private playlists, saved library state and region-gated catalogue items are outside the reach of this build by construction. The disclaimer reinforces the boundary, calling SpotiFLAC a third-party tool that is not affiliated with, endorsed by, or connected to Spotify, Tidal, Qobuz, Amazon Music or any other streaming service, which means you get no notice and no support when any of those endpoints change.

Three numbered clauses put local law, platform terms and consequences on the user

The disclaimer states that the project is for educational and private use only and that the developer does not condone or encourage copyright infringement. It then assigns responsibility in three numbered lines: ensuring your use complies with your local laws, reading and adhering to the Terms of Service of the respective platforms, and any legal consequences resulting from misuse of the tool. The software is provided as is, without warranty of any kind, and the author assumes no liability for bans, damages or legal issues arising from its use. What that means in practice is that the project takes no position on which use is acceptable, so there is no guidance to appeal to when you decide whether your own download of a given track is inside or outside your subscription's terms. The absence of any account requirement does not change the reading, since the terms of service reach the audio rather than only the login. There is also no bulk or automation guidance in the README, so the rate limit documented above is the only throttle on how much you pull.

Four projects share the name, and release numbers do not travel between them

Before you file a bug or ask for help, work out which of the four things you installed. The desktop build you get from the release page covers Tidal, Qobuz and Amazon Music. SpotiFLAC-Next is a separate repository that describes itself as getting Spotify tracks in true lossless from Tidal, Qobuz, Amazon Music and Deezer, so Deezer coverage lives there. SpotubeDL.com is a different project again, aimed at downloading tracks, albums, playlists and discographies as MP3, OGG or Opus rather than FLAC. The Android and iOS build by @zarzet and the Python library by @BartolomeoRusso9 are community projects with no shared version scheme, and the README's note that related projects are not affiliated with the core desktop build is the reason support does not carry across. Timing matters too: the recent tags are v7.2.0 on 2026-07-18, v7.2.1 on 2026-08-11 and v7.2.2 on 2026-08-17, and the last push to main landed on 2026-08-17, with release notifications routed through the GitHub releases page and a Telegram channel.

Editorial conclusion

SpotiFLAC fits a listener who wants a local lossless copy of one track and is comfortable with an unsigned build, a rate limit keyed to their IP, and no account anywhere in the chain. It does not fit anyone who needs a library they can re-download later, who works on a machine with enforced antivirus, or who needs a guarantee that the upstream endpoints will still exist next month. Before you install, read the disclaimer, because the project puts local law, platform terms of service and every legal consequence on the person running it, and build from source yourself if the packaged executable is going to be quarantined.

Frequently asked questions

Is SpotiFLAC safe?

The project says the software is completely free, needs no account, login or subscription, and only requires an internet connection. It has no connection to your Spotify account, because Spotify data comes from reverse engineering the web player instead of user authentication. The disclaimer limits it to educational and private use and provides it as is, without warranty of any kind.

What does SpotiFLAC do?

It gets Spotify tracks in true FLAC from Tidal, Qobuz and Amazon Music with no account required. The audio is fetched using third-party APIs, and the metadata side draws on credited services including MusicBrainz, LRCLIB, Songlink/Odesli and Songstats.

Why does SpotiFLAC not work?

The documented cause is rate limiting: metadata fetching usually fails because your IP address has been rate-limited. The project's own advice is to wait and try again later, or to use a VPN to bypass the rate limit.

is spotiflac open source

The repository is MIT licensed and carries the whole application, with main.go, app.go, a backend directory, a frontend directory, go.mod and go.sum at the top level. The README points anyone worried about the packaged binary to fork the repository and build the software from source, and go.mod declares module github.com/spotbye/SpotiFLAC.

spotiflac vs spotiflac next

The desktop build in this repository draws from Tidal, Qobuz and Amazon Music. SpotiFLAC-Next is a separate project that adds Deezer to that same source list and advertises true lossless output, while SpotubeDL.com is a separate site for MP3, OGG and Opus downloads of tracks, albums, playlists and discographies.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. spotbye/SpotiFLAC on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/spotbye-spotiflac.svg)](https://hysenlabs.com/projects/spotbye-spotiflac)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/spotbye-spotiflac.svg)](https://hysenlabs.com/projects/spotbye-spotiflac)

Was this useful?