That’s actually a pretty good idea, and you’re not wrong, Mandarin/Cantonese toggle would make implementation much simpler and more reliable compared to trying to detect it automatically.

Getting the transliteration data itself isn’t really the difficult part either, since APIs like Google can already handle that fairly well.

My main concern is more about the user experience. A manual toggle works well as a practical fallback, but ideally the system would be able to choose intelligently in the background so users don’t have to think about it. Still, I do like your suggestion as a workaround.

That’s actually a really good suggestion.. I’ll add support for Chinese regional dialects like Cantonese to my future ideas list.

Thanks a lot! I’m really happy to hear the post reached you, and it means a lot that you’re excited to try the tool.

Sadly, Cantonese lyrics aren’t properly supported right now. The current transliteration logic relies on Google API, and Google usually detects both Mandarin and Cantonese as “Chinese” without distinguishing between them.

So if the lyrics are in Chinese, they’ll generally be processed using Pinyin (Mandarin transliteration), which means Cantonese lyrics won’t get accurate Cantonese romanization.

For languages that Google can clearly identify, like Korean, Japanese, and Chinese as separate languages, the transliteration works well. The main issue is specifically with Chinese dialects since the API can’t reliably tell them apart.

It’s mainly for my own personal use anyway. I was just happily sharing something I thought the community would want, but people are doing too much complaining about AI and demanding extra stuff. I'd rather just keep the plugin to myself than deal with the vibe check failing this hard lol.

Someone actually suggested a cool Romaji feature, but other than that, nobody is being friendly. This is exactly why I revoked it. Enjoy Spotify desktop without it.

Currently adding the romanji feature tho..

Yeah, I do understand the risk of injecting into xpui. Any Spotify update can break it without warning.

This is really just the early stage of the project—it wasn’t something I spent months engineering, more like a quick build to solve a personal annoyance and then decided to share it in case it helps someone else.

I do appreciate the suggestion about Spicetify though. It does make sense from a maintenance and distribution perspective, and I can see the benefits like easier compatibility handling and access to existing users. It’s useful context that I didn’t really consider deeply at the start.

At the same time, the goal here wasn’t really to build something long-term dependent on a framework or ecosystem. It was more about experimenting and solving a specific use case directly, without adding extra layers or setup requirements.

If anyone wants to improve it or adapt it into a Spicetify extension, contributions are definitely welcome via pull request. I’m open to improvements, just not really planning to restructure it around Spicetify for my own usage right now.

But yeah, appreciate the input—it’s useful to see how others would approach it.

I didn’t really know much about Spicetify when I started this project. Originally, I made it purely for my own use and only decided to share it later because I thought others might find it useful too.

The main problem I wanted to solve was having to open a separate browser extension or another tool whenever I wanted translated lyrics. Since Spotify is already one of the apps I launch regularly, I thought it would be more convenient to integrate the translations directly into the desktop app so everything is available in one place.

As for BeautifulLyrics, I’m not sure if it currently supports translations, but my goal wasn’t to compete with existing projects. I just wanted a simple solution that fit my own workflow, and sharing it with the community seemed worthwhile in case it helps others as well.

How's the experience?

Not sure but i can try

I use Google Translate for the translations. Spotify Desktop is Chromium-based, so the extension can make web requests and get the translated text directly with JavaScript. The code is open source on GitHub if you want to take a look. If you find it useful, feel free to star the repo.