Welcome back to Feature Friday. We’ve walked through the sound engine and sharing with friends — this week it’s the fun one: making Veilamp yours. There are two layers to that. You can change how the player looks (skins), and you can change what the player does (plugins). Let’s take both.

A skin is just a small file

Under the hood, the entire Veilamp UI is driven by a set of CSS variables — colors, gradients, fonts, corner radius, the lot. So a skin is mostly a tiny file that remaps those variables to your taste, plus an optional block of raw CSS for anything the variables don’t cover.

The nice part is how little you have to do. A skin can be as small as one override — change the primary accent from cyan to amber and ship it; everything you don’t touch falls back to the default “Neon Glass” look. There’s a built-in “Download an example color theme” button that writes out a file already listing every variable, so you can start from a full palette and just edit the colors.

You get real reach, too:

  • Colors and glow — the cyan/magenta/amber accents, the neon glow strings, the gradients behind buttons, every background shade.
  • Fonts — swap the UI font, the big LCD display font, and the monospace font.
  • Icons — replace any action icon with your own SVG; it still picks up the surrounding text color automatically.
  • The window itself — round the corners however you like, or hand it a clip-path and get a genuinely non-rectangular window. The frame is transparent, so the clipped-away bits show your desktop right through them.
  • Variants — ship one theme with several accent options (say, Cyan / Amber / Magenta) that the user flips between with a click, and Veilamp remembers their pick.

Add one from Settings → Appearance → + Add skin…, or just drop the file onto that screen. If your skin needs bundled fonts, background art, or custom icons, package them together as a folder or a .zip (with an optional preview image for the picker) and Veilamp wires up all the file references for you — no fiddling with inlined data URIs.

Rearrange the whole player — no code

Recoloring is one thing. A skin package can also ship a custom layout: a complete re-arrangement of the player. Want the album art huge up top, a spectrum strip under it, the transport controls down one side, and the playlist filling the rest? You can build exactly that.

And here’s the thing we’re proud of — it’s declarative, not code. You describe a tree of built-in widgets (album art, seek bar, VU meters, spectrum, transport, playlist, a wall clock, even radial tick-mark dials) arranged in simple boxes, and Veilamp renders its own real, state-connected components into your design. That means a custom layout is exactly as safe as a plain theme — there’s no program running, just an arrangement. You can even wire buttons to real actions and have the layout react to what’s playing (progress, volume, play/pause state) straight from CSS.

Yes, your old Winamp skins work

This one’s for the long-timers. Veilamp imports classic Winamp 2.x .wsz skins. Drop one in and it decodes the old sprite sheets, rebuilds the authentic stacked main-window-over-playlist look, and wires the transport, seek bar, volume, shuffle/repeat, playlist, and the equalizer window up to Veilamp’s actual engine — the song title and timer render live in the skin’s own pixel font, the EQ sliders drive the real 10-band EQ.

We don’t ship any Winamp skins ourselves (they rarely come with a license to redistribute), so bring your own — the Winamp Skin Museum at skins.webamp.org has tens of thousands of them. Pick one, import it, respect its license. Decades of skin art, running in a modern privacy-first player.

Plugins: teach it new tricks

Skins change how Veilamp looks and arranges itself, but they can’t add genuinely new behavior. That’s what plugins are for — small JavaScript programs that run against a stable window.veilamp API. A plugin can add its own panel (a tab with its own UI — a lyrics box, a stats readout, a custom now-playing display) or a custom visualizer that draws to a live audio feed and shows up as its own mode on the Visualizer screen.

They can read what’s playing, follow the live spectrum frame by frame, look things up in your library, drive transport, react to the active theme so they recolor with the rest of the app, and save their own settings. Folks have already built everything from cozy little panels to, well — yes, someone got Doom running in there.

Powerful, but on a short leash

Here’s the part that matters, and the part that’s very Veilamp: plugins are untrusted by default. Each one runs in its own locked-down sandbox with no access to the rest of the app, no cookies, and — this is the big one — no network access at all unless you say so.

Every capability is a switch you flip. A plugin can ask for permission to see your library, or control playback, or reach a specific website, but asking is all it can do. Nothing is granted until you tick the box in Settings → Plugins, and if a plugin wants to talk to the internet it has to name exactly which sites up front — then only those are ever allowed, and nothing else. A visualizer that just draws pretty bars never needs to see your library or touch the network, and by default it can’t. Your music, your machine, your call — same principle as the rest of the app.

There’s a whole directory of this stuff

You don’t have to start from a blank file. We run a community skins & mods directory right here at veilamp.com/skins — browse what other people have made, grab a palette or a layout or a plugin, and install it in a couple of clicks. Made something good? There’s a link on that page to submit it, and we’ll pull it in.

So that’s your weekend assignment: open Settings → Appearance, recolor the whole player in five minutes, maybe dig an old Winamp skin out of the museum, and poke around the directory. Make it look like yours.

Next Friday we’ll pick another corner of the app. If there’s something you want us to dig into, tell us.

Until then — happy listening.