Mac Help Centre

The website currently provides Live Chat, WhatsApp and the external VstPluginz knowledgebase. Paid-order and eligible VIP install help can also be handled remotely when appropriate.

When contacting support, send: product title, Windows/macOS version, DAW/version, screenshot of the exact error, payment reference if relevant, and what you have already tried.

VstPluginz advertises remote install assistance for eligible purchases and members. Before a remote session:

• Close banking, email, password-manager and private documents.
• Only accept the connection after you have contacted the official VstPluginz support channel yourself.
• Watch the session and ask what is being changed.
• End the session and close the remote-access app when finished.
• Never send account passwords, bank PINs, recovery codes or two-factor codes in chat.

The VstPluginz refund policy is support-first: the team may verify the problem, help with installation, offer a compatible/replacement version, or use remote assistance before a refund is considered.

The site search supports broad searches and category filters. Useful catalogue routes include Windows, Mac OSX, MUSIC, Samples, Presets, Libraries, MiDi, Projects/Templates and Bundles.

• Use the exact developer name when you know it.
• For sample/music results, use the genre filter as well as text search.
• If a specific search is empty, remove one filter and search more broadly.
• The Mega Menu includes FREE PRODUCTS and SEARCH EVERYTHING.

Check the category/OS and product information before buying or downloading. For MUSIC listings, the site reports the file information as Full Length Tracks. Other products may contain installers, libraries, presets, samples, documentation or multiple packages.

The top navigation contains Favoritez and Basket. The basket workflow is account-aware, so logging in gives the cleanest purchase history and download experience.

If the site appears logged out unexpectedly, refresh once, then open My Account. If needed, log in again rather than repeatedly refreshing checkout pages.

1. Hard refresh the page.
2. Try a private/incognito window.
3. Disable content blockers for vstpluginz.com.
4. Make sure JavaScript and cookies are allowed.
5. Try another browser before changing system settings.

Windows: Ctrl + F5. Mac: reload Safari/Chrome and, if necessary, clear site data for vstpluginz.com only.

Use the hamburger menu for navigation. The new HELP CENTRE link is placed at the top of the mobile menu so users can reach troubleshooting without scrolling through the catalogue navigation.

VstPluginz uses a unified checkout entry. The active payment provider is selected by site administration, so an end user may see a WorldPay- or SumUp-powered payment experience without needing to choose a gateway manually.

Single-product purchases, baskets and VIP all use the same gateway decision.

If the provider is still confirming a payment, do not submit another payment. Keep the payment reference and wait for the provider confirmation. Check the success page, email, My Account and the floating Download menu.

1. Check billing details and available funds.
2. Turn off aggressive ad/script blockers for the checkout page.
3. Try a private/incognito window.
4. Try another modern browser.
5. Do not use an old bookmarked payment URL.
6. If the payment provider rejects the card, contact the bank or VstPluginz support.

After a successful paid product checkout, VstPluginz can provide the download in several places:

• the success page immediately after checkout;
• the purchase email;
• the floating Download menu in the top navigation;
• My Account purchase history when the purchase can be associated with your account.

If one route fails, check the others before buying again.

Where the unified success flow offers Resend Email, you can resend the download message to a valid email address. The current anti-abuse system allows a limited number of attempts and applies a short cooldown between resends.

If the resend limit is reached, use Live Chat/WhatsApp and provide your payment reference.

• Search your mailbox for VstPluginz.
• Check Spam, Junk, Promotions and Quarantine folders.
• Mark the genuine order email as “Not Spam”.
• Confirm the email address entered at checkout.
• Use Resend Email if shown.
• Use My Account / Download menu if email is delayed.

The current VstPluginz paid download system uses a 48-hour download window. Download the files promptly and keep your own local backup after extraction.

Successful purchases and eligible VIP downloads can be pushed into the floating Download control in the top navigation. It is a convenience layer for active download links and their remaining time.

If you dismiss an item from the menu, that does not necessarily delete your account purchase record.

VstPluginz sends the file to the browser. The browser decides the local save location. Most systems use the Downloads folder unless you changed it.

• Chrome/Edge: press Ctrl+J (Windows) or ⌘+Shift+J/⌘+Option+L depending on browser version, or use the Downloads menu.
• Safari: click the Downloads arrow near the address bar, then the magnifying glass to reveal in Finder.
• Firefox: click the Downloads arrow or open the Downloads Library.

1. Delete the incomplete file.
2. Confirm enough free disk space is available.
3. Download again on a stable connection.
4. For multi-part archives, make sure every part finished successfully.
5. Do not rename individual parts.
6. Try another browser if the same file repeatedly truncates.

Product pages include a REPORT A DEAD LINK route, and the downloader can surface an alternative-link request when a provider cannot prepare a file. Use those controls rather than repeatedly hammering the same link.

For a paid order, contact support with the product title and payment reference so the order can be handled personally if necessary.

• Use a wired/stable Wi‑Fi connection where possible.
• Prevent the computer from sleeping during a very large transfer.
• Make sure the destination drive has substantially more free space than the archive size; extraction can require 2× or more temporary space.
• A VPN or corporate proxy can make large downloads less stable; test without it if permitted.

1. Open Chrome Settings.
2. Go to Privacy and security → Site settings.
3. Open Additional permissions → Automatic downloads.
4. Allow the setting needed for trusted sites, or add vstpluginz.com to the allowed list if Chrome offers a site-specific option.
5. Open chrome://downloads to inspect interrupted files.

1. Open Settings → Downloads.
2. Check the download Location.
3. Enable the option to ask where to save each file if you want manual control.
4. Press Ctrl+J to open the recent downloads list.

Open Firefox Settings → General → Downloads / Files and Applications. Choose the save folder and whether Firefox should ask what to do with files. Use the Downloads panel to resume or reveal a file.

1. Open Safari and visit VstPluginz.
2. Open the page/website settings for the current site.
3. Check the site’s Downloads permission and choose Allow if Safari is blocking it.
4. Open Safari → Settings → General to choose the download folder.
5. Use Safari’s Downloads button to resume or reveal a file in Finder.

If Safari turns a product page into a white simplified article and the address bar says Reader Available, Reader mode or a browser extension is likely involved.

1. Open the product page.
2. Choose Safari → Settings for This Website.
3. Turn Use Reader When Available OFF.
4. Also check Safari → Settings → Websites → Reader and set vstpluginz.com to Off.
5. Temporarily disable content-blocker/Reader extensions and reload.

Safari can automatically open “safe” file types after downloading. That is convenient for a single ZIP but can interfere with multi-part archive workflows.

1. Open Safari → Settings → General.
2. Turn off Open “safe” files after downloading.
3. Download all archive parts first, then extract them together with Keka/The Unarchiver.

Privacy extensions, script blockers, aggressive antivirus browser add-ons and download managers can interfere with payment widgets or file delivery. Test a private window with extensions disabled, or whitelist vstpluginz.com temporarily.

Modern macOS uses Gatekeeper to check downloaded apps, plug-ins and installer packages. VstPluginz does not recommend leaving Gatekeeper globally disabled.

1. First re-download the file; a genuinely damaged download and a security/quarantine issue can look similar.
2. Make sure the archive was completely extracted.
3. Check the app with the Gatekeeper/code-signing diagnostic commands in the Terminal section below.
4. If the file is trusted but macOS still blocks it, use Privacy & Security → Open Anyway where available.

Older tutorials often tell users to disable Gatekeeper system-wide from Terminal. That changes protection for every downloaded application, not just the file you are troubleshooting, and behaviour differs across current macOS releases.

This Help Centre deliberately uses Apple’s supported Open Anyway workflow plus app-specific diagnostics instead. You can check whether Gatekeeper assessment is enabled with:

spctl --status

On an Apple-silicon Mac, older Intel-only apps or plug-ins may require Rosetta. Apple recommends using updated Universal/Apple-silicon versions wherever possible.

1. Finder → select the app → File → Get Info.
2. Check Kind: Intel, Universal or Apple silicon.
3. If an Intel app needs Rosetta and it is not installed, macOS normally prompts you when opening the app.
4. Some Universal DAWs offer Open using Rosetta in Get Info so Intel-only plug-ins can load.

uname -m
sw_vers

Some installers or library managers need access to Documents, Downloads, removable drives or protected locations. Check System Settings → Privacy & Security and grant only the permission the trusted app genuinely needs. Avoid giving Full Disk Access to unknown software.

You do not need the full Xcode app for many Terminal utilities. Apple provides a smaller Command Line Tools package.

xcode-select --install

After installation, verify the active developer-tools path:

xcode-select -p

1. Install Xcode from the Mac App Store.
2. Open Xcode once and allow it to install required components.
3. If Terminal is pointing at Command Line Tools instead of Xcode, select Xcode’s developer directory.

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
xcodebuild -version

These commands inspect an app; they do not change it.

Verify signature structure

codesign --verify --deep --strict --verbose=2 "/Applications/Example.app"

Display signing details

codesign -dv --verbose=4 "/Applications/Example.app" 2>&1

Ask Gatekeeper to assess the app

spctl --assess --type execute --verbose=4 "/Applications/Example.app"

Ad-hoc signing can repair a local signature in some specialist workflows, but it is not Apple notarisation and can break entitlements, updates or licensing. Only do this when the software developer or VstPluginz support has confirmed it is appropriate for that exact file.

codesign --force --deep --sign - "/Applications/Example.app"

If a DAW is native Apple silicon but a plug-in is Intel-only, the plug-in may not appear unless the DAW supports bridging or is opened using Rosetta.

file "/Library/Audio/Plug-Ins/VST3/Example.vst3/Contents/MacOS/Example"
lipo -archs "/Library/Audio/Plug-Ins/VST3/Example.vst3/Contents/MacOS/Example"

Downloaded files can carry quarantine metadata. Inspect it before deciding what to do:

xattr -l "/Applications/Example.app"

If you are not sure what the output means, send it to support rather than removing attributes across your whole Applications folder.

Finder can usually extract a normal ZIP by double-clicking it. For RAR, 7Z and complex/multi-part archives, use Keka or The Unarchiver.

1. Download all parts to the same folder.
2. Turn off Safari’s automatic “safe file” opening while collecting parts.
3. Keep all filenames unchanged and consecutive.
4. Open the first part in Keka/The Unarchiver.
5. Extract to a local folder with enough free space.

Some plug-ins install into the same folders inside your user Library: ~/Library/Audio/Plug-Ins/....

• Logic Pro/MainStage: Audio Units (AU).
• Pro Tools: AAX.
• Ableton/Cubase/Studio One/FL Studio/REAPER: VST3 is generally the modern cross-platform choice; install AU/AAX only when your DAW needs it.
• Do not mix 32-bit plug-ins into a modern 64-bit-only DAW.

When the installer lets you choose several formats, installing only the formats you actually use keeps scans faster and reduces confusion.

Open Live Settings/Preferences → Plug-Ins. Enable the relevant AU/VST2/VST3 sources and confirm any custom VST2 folder points to the actual install location. If a plug-in is still missing, toggle the source off/on or use a deep rescan by holding Alt/Option while clicking Rescan.

In Logic Pro choose Logic Pro → Settings/Preferences → Plug-In Manager. If a newly installed AU is missing, use Full Audio Unit Reset, close Logic, reopen it and allow the validation scan to complete.

Open Options → File settings → Manage plugins. Use Find installed plugins / scan, and use Verify plugins when you need FL Studio to categorise generators and effects correctly. Confirm any extra VST2 search folder matches the installer destination.

Open Studio → VST Plug-in Manager. Use Scan for new and blocked plug-ins. Current Cubase versions are 64-bit, so old 32-bit plug-ins will not load.

Windows: Options → Locations → VST Plug-ins. Mac: Preferences → Locations → VST Plug-ins. Confirm custom VST2 paths and use the plug-in manager/blocklist controls if a known-compatible plug-in is missing.

Pro Tools uses AAX. Current standard locations are /Library/Application Support/Avid/Audio/Plug-Ins on Mac and C:\Program Files\Common Files\Avid\Audio\Plug-Ins on Windows. If a plug-in is missing, confirm it is not in the Plug-Ins (Unused) folder and is a compatible AAX build.

Open REAPER Preferences and find the VST/plug-in paths section. Add the folder containing your VST plug-ins, then use Rescan/Clear cache and rescan when necessary.

A Kontakt library is content loaded by Kontakt; it is not normally copied into your VST3 folder. Use the installation/registration method provided by the library developer. Libraries made for Kontakt Player generally use Native Instruments' supported registration workflow; other third-party libraries may be loaded from Kontakt’s Files/Browser according to their documentation.

Preset folders are product-specific. Open the synthesizer and use its own Show preset folder / Open user folder / Import preset command when available. Do not place presets into generic VST folders.

WAV/AIFF loops and MIDI files usually do not require installation. Extract them to a permanent library folder, then add that folder to your DAW browser or drag files directly into a project. Keep the original pack folder structure if it contains MIDI, one-shots, loops and presets together.

The current VIP success flow records the purchase and tells users that admin activation is normally completed within a few hours. A second email is sent when access is activated. Check Spam/Junk if the confirmation email is missing.

Your membership package includes the VIP download allowance shown in the VIP Packages, Prices & Member Benefits table above. In addition, active members can download 20 FREE music tracks per day and 5 FREE products per day.

Re-downloading the same eligible VIP product is handled separately by the site's existing re-download rules. Check My Account for the live membership and quota currently attached to your account.

No. The current VIP logic records unique products and tells users that re-downloading the same product does not use another quota credit.

The product page warns when you reach the last three download credits. If the quota is exhausted, the download button is blocked until your plan resets (where applicable) or the account is upgraded/renewed.

The account page treats main-site VIP product downloads and the separate vstpluginz.vip torrent/download system as different quota systems. A torrent/VIP-site download does not automatically consume the main-site allowance.

Active VIP members can download 20 FREE full music tracks per day and 5 FREE products per day. The site also provides the Beatport-powered VIP Music browser for music discovery and previews.

1. Confirm you installed the format your DAW supports.
2. Confirm it went to the correct plug-in folder.
3. Confirm your DAW is 64-bit and the plug-in is compatible.
4. On Apple silicon, check whether the plug-in is Intel-only.
5. Run the DAW’s plug-in rescan.
6. Check the DAW blocklist/failed-validation list.
7. Restart the DAW after installation.

A single incompatible plug-in can crash a scan. Note the last plug-in name shown before the crash, move that plug-in temporarily out of the scan path, then reopen the DAW. Update the plug-in and verify OS/CPU compatibility before putting it back.

Ableton can be launched with plug-in scanning temporarily disabled by holding Alt/Option during launch.

• Check track input/output routing and monitoring.
• For instruments, confirm MIDI is reaching the track.
• Confirm the instrument/library finished loading its samples.
• Check the DAW audio device and sample rate.
• Try the plug-in in a blank project.
• Check whether a demo/trial or older conflicting installation is still present.

Large libraries can need much more space than the compressed download. As a rule of thumb, keep at least enough room for the archive plus the fully extracted content plus temporary installer files. If using an external drive, use a filesystem supported by your OS and do not disconnect it while the DAW is running.

Do not force-install blindly. Check the product’s stated OS, plug-in format and CPU requirements. Audio workstations are especially sensitive to major macOS/Windows upgrades. If your system is newer or older than the product expects, contact support for a compatible version before changing security settings.

Modern browsers restrict autoplay. Click/tap a Play control once to give the page a user gesture. If previews still fail, check the browser tab is not muted, site audio is allowed, and content blockers are not blocking media requests.

• Product title and VstPluginz product ID/list ID.
• Windows 10/11 or exact macOS version.
• Intel/Apple silicon on Mac.
• DAW name and version.
• Plug-in format being installed (VST2/VST3/AU/AAX).
• Exact error text or screenshot.
• Archive filename and whether it was multi-part.
• Payment reference for paid-order delivery issues.

This video is already referenced inside the VstPluginz support/download system.

Use the dedicated site pages for the current policy wording. Help guides do not replace those pages.