Help Center

No account is required to download or use the plugins. If you buy a license, the license key is sent by email. You can optionally use a secure login link to view your purchases and downloads, but it is not required for plugin use.

No. MousePlugins currently supports Windows 10/11 64-bit and Linux x64 only.

The plugins do not collect telemetry, phone home, send crash reports, or track DAW activity. Plugin activation is local/offline after you receive your license key. The website may use privacy-friendly aggregate analytics, but the plugins themselves do not send usage data.

MousePlugins is developed by Stéphane Berger, an independent developer based in Spain. It is a small solo operation focused on DSP tools, plugin design, and practical support.

MousePlugins supports VST3 and CLAP. CLAP is an open plugin format supported by hosts such as Bitwig and Reaper. VST3 is provided for DAWs that support the VST3 format.

No iLok, no dongle, and no hardware license device is required. Licensing uses a license key stored locally by the plugin.

Payments are handled through Stripe Checkout. Available payment methods depend on your region and may include card payments, Apple Pay, Google Pay, or other Stripe-supported options. The checkout process provides the receipt and license delivery.

Email support@mouseplugins.com. MousePlugins is a solo operation, so response times may vary, but support requests are reviewed as soon as possible.

Yes. More plugins are planned and in development. Release dates are only announced when a plugin is ready to ship.

We use Stripe for checkout. Stripe accepts major credit and debit cards, Apple Pay, Google Pay, and a few regional methods depending on your country. You will see the available options on the checkout page.

Yes, where required. The checkout page shows the applicable tax for your billing country before you confirm. EU buyers normally see VAT applied at their local rate. Buyers outside the EU may see no tax or a local tax depending on the checkout rules for their country.

A confirmation email arrives after payment. Your licenses and downloads are available from your account dashboard after signing in. If the email includes direct links for a product, those links point to the same files shown in your dashboard.

Yes. The payment confirmation email doubles as a receipt. For a formal invoice with your company details, reply to the confirmation email or write to support@mouseplugins.com — we can re-issue with your company name, VAT number, and address.

An account is created automatically as part of checkout, using the email you provide. There is no second signup step. You can sign in later with that email to access your licenses and downloads.

Yes. If a plugin does not work for you, contact support@mouseplugins.com within 14 days of purchase. We will either help you solve the issue or issue a refund. Refunds go back to the original payment method and typically clear in 5-10 business days.

No. Personal licenses are tied to the buyer and not transferable. If you bought a license for a different person by mistake, contact support and we will sort it out.

A personal license covers unlimited installations on machines you personally use. There is no per-seat counting and no online check.

Not yet. We will publish any future student / studio / volume pricing on the product pages when it exists.

MousePlugins is run from Spain (EU). Our payment processing is via Stripe Ireland.

VST3 goes in `C:\Program Files\Common Files\VST3\` and CLAP goes in `C:\Program Files\Common Files\CLAP\`. Copy the `.vst3` and `.clap` files or folders from the package into those paths.

VST3 goes in `~/.vst3/` (per-user) or `/usr/local/lib/vst3/` (system-wide). CLAP goes in `~/.clap/` or `/usr/local/lib/clap/`. Linux distributions vary by DAW preference — Bitwig and Reaper both scan the per-user paths by default.

Windows packages are supplied as a zip file with README installation notes. Linux packages are supplied as a tar.gz archive that you extract into the plugin folder of your choice. If installers are added for a product later, the product download page will say so clearly.

First, confirm the file is in the format folder your DAW scans (see above). Then rescan plugins from the DAW preferences. On Linux, confirm the plugin bundle or binary has executable permissions. If your DAW only supports AU or AAX, the plugin will not appear there because those formats are not currently shipped.

On Linux, use a modern 64-bit distribution such as Ubuntu 22.04+, Debian 12+, Mint 21+, Fedora 36+, Pop!_OS 22.04+, recent Arch / Manjaro, or openSUSE Tumbleweed. Technically, the system needs glibc 2.35 or newer. Windows 10 / 11 (64-bit) does not require any additional runtime or library.

Yes. A personal license covers all machines you personally use. Copy the license file to each machine; no online activation is required.

Remove the plugin files from the folders where you installed them. On Windows, delete the `.vst3` and `.clap` files or folders from the common plugin locations. On Linux, delete the `.vst3` and `.clap` files from the plugin folder you used.

Yes. Sign in to your account and re-download the package. The license covers all included formats.

Activation is offline and does not require an account. You receive a license key, enter it in the plugin, and the plugin stores the activation locally. No internet connection is required for activation or normal use.

You may install the plugin on your own personal devices, such as your studio computer, laptop, or home system. The license is personal to you and the license key must not be shared with other users.

Email support@mouseplugins.com with your order details and we will help recover or reissue the license information where possible.

You only need to be online to purchase the plugin and receive your download/license email. After that, the plugin runs offline and does not require an internet connection for normal use.

Yes. You may use the plugin for commercial music production, client work, released tracks, and paid projects. The license is perpetual and does not place restrictions on the audio output you create with the plugin.

Updates within the same major version are included. For example, v1.0 to v1.5 to v1.x updates are covered. A future major version upgrade, such as v1 to v2, may be sold separately if it introduces a major new version.

The Terms of Service and Privacy Policy are linked in the website footer and during checkout. They include the current purchase, refund, licensing, and privacy rules.

Licenses are personal and are not generally transferable. If you have a specific situation, email support@mouseplugins.com and we will review it case by case.

Yes. Updates for a plugin you own are free for as long as that product is maintained and sold by MousePlugins. There is no maintenance subscription and no upgrade fee for point releases.

Sign in to your account dashboard. The Downloads page shows the latest version for every product you own, with an "Update available" badge if you have a previous version registered. Release notes are available alongside each version.

Download the new package and extract it over your existing plugin folder, replacing the previous version. Project files that reference the plugin continue to load.

We take backward compatibility seriously and test saved project states across updates. Existing projects should continue to load with their saved settings. If a change requires special handling, we document it in the release notes.

Each plugin's product page has a Releases tab. There is also a global feed at `/en/releases` that lists every release across the line.

No. There is no auto-updater and no background service. You choose when to download and install.

Windows 10 and 11 (64-bit) and Linux x86_64 with glibc 2.35 or newer. macOS is not currently shipped.

VST3 and CLAP. The same license covers both.

Not currently. VST3 and CLAP only.

The plugins are built for hosts that support VST3 or CLAP. We test with common hosts such as Bitwig Studio and REAPER, and VST3 hosts such as Cubase, Studio One, Ableton Live, FL Studio, and Mixbus should load the appropriate format. If a host has special scanning or format limitations, check the host's plugin settings.

44.1, 48, 88.2, 96, 176.4, and 192 kHz across the line. Oversampling, where present, is per-plugin and explained on the product page.

A 64-bit x86 processor is required. Specific CPU requirements may vary by product and oversampling mode — the product page lists the recommended setup for each plugin. RAM use is small across the line; the plugins are DSP-only and do not load large sample libraries.

No. 64-bit only on both Windows and Linux.

Yes. In v1.1.0, the plugin window supports free resizing: drag the window edges or corners to make the interface larger or smaller. The plugin remembers the window size and restores it the next time it opens.

Yes. The UI scales cleanly on high-DPI Windows displays and HiDPI Linux desktops. Free resize lets you match the plugin to whatever fits your screen comfortably.

Yes. Every paid plugin has a fully functional demo with periodic short demo interruptions. All controls, all modes, and all features are available. The demo is meant to let you decide whether the plugin fits your workflow before buying.

The demo does not expire. You can keep it installed indefinitely; the periodic demo interruption is the only difference from the licensed version.

Offline renders are subject to the same demo interruption as live playback, so they are not a substitute for the licensed version on a real session.

Yes. Once you activate the licensed version, the demo interruption stops and all your existing project files, presets, and saved settings carry over.

No. Download the demo from the product page, install it, load it in your DAW.

Nothing else runs in the background. Remove the plugin files from the folders where you installed them, and the trial is gone.

Yes — 14 days from the purchase date. See the Purchases section for details.

Confirm the file is in the format folder your DAW scans. Rescan plugins from DAW preferences. On Linux, confirm the file has executable permissions. If your DAW only supports AU or AAX, the plugin will not load — VST3 / CLAP only on Windows and Linux.

Try downloading from a fresh browser window or a different network. If the issue persists, write to support@mouseplugins.com with the filename, size, and your operating system — we will check the artifact server-side.

Check that the host is sending audio to the plugin (the input meter should move). Verify the plugin's Master Bypass is off, and that the Mix knob (where present) is not at fully dry on a parallel processor.

Most updates preserve saved state, but defaults or processing details may change between versions. Existing projects should load with their saved settings. Check the release notes for any sound-affecting changes. If something seems wrong, contact support with the product, version, host, operating system, and a short description.

Sign in to your account dashboard. The license is downloadable again from the Downloads page for each owned product.

Confirm the license file is in the correct location (mentioned in the welcome email per platform). Re-download a fresh copy from your account dashboard. If the issue persists, write to support@mouseplugins.com with your account email and the affected product name.

Try resizing the window by dragging a corner or edge. If the window still does not render, close the DAW project, re-open it, and reload the plugin. On Linux, a missing graphics driver can cause blank panels — confirm OpenGL is available.

Check the Quality / oversampling setting on the plugin's footer readout. Master 8x is heavier than Live 1x; switch to a lower-CPU mode while tracking and raise the quality at mix time.

Dropouts are usually related to buffer size, CPU load, or the host audio driver. Increase the audio buffer size, close other CPU-heavy plugins, and lower the plugin Quality / oversampling mode if available. If the issue continues, contact support with your host, operating system, sample rate, buffer size, and plugin version.

Use the Leave feedback button on the relevant product page (you need to be signed in). Or write to support@mouseplugins.com directly. We read every submission and use it to plan the roadmap.