November 16, 2026
Klevgrand’s New Update Adds a Resizable GUI and a Freeze Button: Worth the Install

The Klevgrand update that added a resizable GUI and a freeze button is the kind of release that gets skipped in a feed full of new instruments. We installed it anyway. After a couple of sessions with it on the master bus and on individual channels, the verdict is simple: the window resize matters more than the freeze button, and both are useful.
Context first. Klevgrand is a Swedish plugin developer, and their line covers processing and instruments. The update in question lands on one of their processor plugins rather than an instrument; the interface can now be dragged to any size, and a freeze function has been added to the processing path. We are judging it the way we judge everything: whether a two-hour set survives it, not whether the first thirty seconds sound impressive.
The resizable GUI is the real headline
Sitting in front of a plugin for the length of a full show is different from auditioning it for five minutes. When a window is fixed, you end up leaning in to read small labels, and on a 27-inch display at working distance, that gets old fast. Dragging the corner to fill a third of the screen and having the controls scale with it is not a feature you celebrate; it is one you stop noticing, which is the point.
The scaling here follows the window without turning into a blur. Labels stay legible, the layout does not fall apart at very wide sizes, and the controls keep their proportions. On a laptop screen it also means you can shrink the thing down to a compact strip and park it next to a meter without stealing the whole workspace. That matters when we are checking gain reduction against a loudness readout across a long block of tracks.
We would not call a resizable interface a reason to buy anything. But once a plugin is in a regular chain, the ergonomics decide whether it stays there. A fixed window slows down every session where it appears; a scalable one disappears into the workflow. That is the honest difference.
What the freeze button actually does
The freeze control halts the plugin’s internal processing at the current state so the CPU stops recalculating it on every cycle. In practice, that means you can dial in a setting you like, freeze it, and free up headroom for the rest of the session.
Two uses are obvious. First, if you are running several instances on a large session and the load is climbing, freezing the ones that are already committed lets you keep working without bouncing anything down. Second, and this is the better one, freezing becomes an A/B tool: set the plugin, freeze, then compare against the unfrozen version by ear while the CPU does nothing. When we are working on a master and want to check whether a processing decision is helping or just loud, being able to lock the state and step back is worth more than any extra feature.
The limitation is the same one every freeze function has: a frozen plugin is not responding to new automation or changing input. If you are processing stems that arrive at different levels across a show, freezing early locks in a setting that may not suit the next track. It works best as a commit tool at the end of a chain, not as a set-and-forget filter in the middle of one.
How we used it across a long mix
Our test session was a small block of tracks prepped for automated playback, which means consistent loudness and no surprises at the transition points. We put the plugin on the master and left it there for the whole pass.
- Set the processing lightly, checked the loudness target against a meter, then froze it while we moved on to editing individual tracks.
- Unfroze when a track needed a different treatment, adjusted, refroze.
- Used the resized window next to a level meter so both were readable without switching tabs.
Nothing dramatic happened. That is the result we wanted. The plugin stayed out of the way, the CPU reading stayed flat because it was frozen most of the time, and the session moved at a normal pace.
Small annoyances
The freeze state is not always obvious at a glance. Once a plugin is frozen, the visual difference from the live state is subtle enough that we caught ourselves wondering whether processing was running during a comparison. A clearer indicator would save a few seconds of doubt. The resize also does not remember a per-project size in every host we tried; some sessions reopened at the default. Neither issue is a dealbreaker, but they are the sort of thing a point release should fix.
Should you install it
If the plugin is already in your chain, install the update. The resizable GUI removes friction from every session and the freeze control gives you a way to commit a setting without bouncing audio. If you do not own the plugin, this update is not a reason to buy it; the feature set is incremental, not a redesign.
Where it earns its keep for us is in the last stage before playback, when a set is locked and the only job left is to stop touching things. A plugin that can be frozen, scaled to a readable size, and left alone for two hours is doing its job. That is a low bar, but plenty of tools fail it.