Turn your own recording into keyboard sounds

Levin • • • #custom keyboard sound packs #import keyboard sounds
Illustrated keyboard switches for a custom sound-pack guide
Quick answer

Choose an app that imports custom keyboard sounds. Check Mechvibes Classic folders, DX editing and pack formats, and Klakk's 14 included sound packs.

Download Klakk

For macOS and Windows. Try all 14 sound packs free for 3 days.

To make your own recording play when you type, choose a keyboard-sound app with a custom-pack editor and import workflow. Mechvibes Classic and MechvibesDX provide routes for custom packs. Klakk’s website editions offer 14 included packs, with no supported user-facing sound-file import or pack editor.

I’m Levin, Klakk’s developer. This guide was prepared with AI assistance and checked against official Mechvibes documentation and Klakk’s current controls on October 11, 2026. It is a documented workflow and choice guide; we have not installed, recorded with or tested every competing app or custom pack.

Decide what you want to add

Your taskStarting point
Add a downloaded Classic-compatible packThe installed Classic version’s custom-pack folder
Map parts of your own recording to keysThe MechvibesDX editor and its V2 export
Choose an included sound with no pack editingKlakk’s browser preview and 14-pack selector

A WAV or MP3 file is the audio source. A pack also describes which keys play which sound or section. Installing the app, importing a pack and assigning sounds to keys are separate operations. Establish the target app and format before moving files.

For a telegraph-like effect, compare a keyboard sound pack with text-to-Morse audio and a manual keyer. An imported sound and a message encoder meet different requirements.

Keep an untouched copy of your recording and original pack. If you plan to share the result, check that you have permission to share the recording; an app’s ability to import an audio file does not establish rights to distribute it.

Check what a custom sound is meant to tell you

A historical typing-trainer request wanted personal audio files for correct input, mistakes, completed words and a new personal speed record. That is a request for conditional practice feedback as well as different sounds. The exact publication timestamp was unavailable in our reading; it does not establish current demand or a learning benefit.

A key-to-file mapping answers which sound a key triggers. The same key can be right or wrong at different positions in an exercise. To distinguish them, the trainer needs the expected text and its scoring rules. The typing-stats comparison explains why background counts and sounds alone cannot grade accuracy.

What you want to customizeCapability to confirm
The sound played for a particular keyA supported audio import and key mapping
A cue when entered text is wrongA trainer’s defined error event and sound control
A reward for a completed word or personal recordThat specific event plus an audio assignment

Monkeytype’s published settings source, checked on October 13, 2026, separates play sound on click, play sound on error and play time warning. Its error setting describes incorrect input or pressing Space too early; the time warning concerns approaching the end of a timed test. Those are different triggers.

The Settings page implementation connects separate click and error choices to previews. A normal click still is not a universal confirmation of correct text: the published feedback logic also uses it for deletion and composition updates, and blind mode affects error-sound selection. Review the mode and input method you intend to practise with. We inspected the public source, without running a test or verifying every deployed browser configuration.

The inspected controls offer built-in sound choices. They do not establish a user-facing uploader for any WAV file or an assignment for every event in the original request. Before paying for custom feedback, confirm both the allowed audio files and the events that can trigger them. Importing a sound pack into a desktop utility does not make that utility a typing trainer.

Klakk’s preview and website trial let you evaluate its included mechanical audio. They do not demonstrate custom-file import, correct-answer cues or word-completion rewards. Choose a practice tool for those requirements; choose a recording library because you enjoy hearing it.

Mechvibes Classic: use the folder for your version

The official Soundpacks wiki recommends the website’s Install button. It still documents manual installation but states that the project no longer supports that method.

For a manual pack, use the app’s tray menu to locate the folder. Before version 2.3.5, the entry is Custom Folder. In 2.3.5 and later, it is Folders → Custom soundpacks. The wiki lists newer application-data locations and older mechvibes_custom locations, so one path copied from a tutorial is not reliable for every version.

Place each unpacked pack in its own folder, with config.json and the audio files immediately inside that pack folder:

custom/
└── my-pack/
    ├── config.json
    └── sound.ogg

An extra nested my-pack folder changes that structure. So does putting the files directly in custom without a pack folder. The wiki’s unextracted ZIP support applies to 2.3.5 and later.

The latest stable release checked on October 11 is 2.3.4; a separately listed 2.3.6-hotfix is a prerelease. Match instructions to the copy you actually installed.

MechvibesDX: edit, export and import

The current official DX editor guide describes Time segments, which assigns sections of a recording, and Sound file per key, which uses separate files. Its documented sequence is:

  1. Use New to create a pack and choose its name and mode.
  2. Load your recording. In Time segments mode, select a section and use Test to preview it.
  3. Select the keys and use Apply to assign the sound.
  4. Use Export to download a V2 ZIP.
  5. In the desktop app, use Settings → Soundpacks → Import Soundpack, then select that keyboard pack.

Importing a pack into the editor prepares it for editing. Importing into the desktop app makes it available for playback. Check the guide for the app version you use if the controls differ.

The DX 0.8.3 format reference uses named keys such as KeyA and Space, and supports OGG, WAV, MP3 and FLAC. In its single-file format, timing pairs specify the start and end of each segment in milliseconds. Classic numeric key definitions should not be copied into DX unchanged.

The 0.8.3 README describes conversion of Classic V1 packs when importing into DX. This is the developer’s documented behavior, not our test of every pack. Keep the original and check the converted assignments. It does not establish reverse compatibility of DX V2 exports with Classic 2.3.4.

Match import changes to a published version

An import feature also has version-specific file-handling behavior. On October 13, 2026, the DX maintainer merged a change to keep imported files inside their pack folder. The maintainer described cases where the previous importer could write outside that folder and added checks on pack IDs and entry filenames. At our check, the latest published release was still 0.8.3, published October 7, before that merge. We have not verified a downloadable build containing the change. A merged source change is therefore not confirmation that your installed release includes it. A separate proposal to refuse imports with an existing pack ID remained open, so do not assume importing a second pack will automatically preserve an earlier one. Keep your original packs and check the release’s documented import behavior before relying on replacement protection. These are attributed development and release observations; we did not run the importer, inspect competing binaries or establish the behavior of every version.

Check the desktop build before choosing DX on Mac

The DX 0.8.3 release page includes a Windows x64 build and a Mac ARM64 DMG, described as ad-hoc signed and not notarized. Its changelog says the experimental and untested labels were removed, but the same release’s bundled Mac README still uses them. These official sources disagree about the testing label; removing a label does not establish that testing occurred. We have not independently tested the Mac build. This release has no Intel DMG. Learning the editor does not confirm that the desktop build suits your Mac.

Thock on Mac: check the pack’s format

If keeping your own audio files matters more than buying a different library, compare the conversion work as well as the player. In a public Mac-app discussion, a reader asked how to make and add custom packs. The maker later pointed to a converter. That historical reply does not mean every existing Mechvibes format becomes an equivalent Mac pack.

The free kamillobinski/Thock 1.23.0 project specifies macOS 13.5+ and publishes a Mechvibes-to-Thock conversion helper. This is a separate script in the project, rather than evidence of a built-in one-click importer for every downloaded pack.

Your original packWhat the published helper establishes
Key definitions name individual audio filesIt maps recognized numeric key codes to Thock names and copies the referenced files
Keys use time intervals inside a shared recordingThis pinned script does not handle those interval-array definitions or extract the sections
You want audio when releasing a keyThe generated definitions have empty release entries and mark key-up support as false

Check the original config.json, rather than assuming that every pack labeled Mechvibes has the same structure. The inspected helper treats definitions as filenames. For a time-segment pack, choose a documented segment-aware route or prepare suitable separate files; changing the player alone does not perform that preparation.

The conversion also does not create missing release recordings. If separate press and release playback is important, compare the actual trigger and pack requirements before choosing a player. A release sound inside a recording is different from a release event starting another sample.

These observations concern the published 1.23.0 helper and documentation, checked on October 13, 2026. We have not run the conversion, installed its app or verified every recording, key mapping and release archive. The project uses an MIT software license; that does not establish rights to every audio file you import. Keep your originals and their notices. Klakk’s included library remains an option when you want to choose its offered packs rather than import your own files.

If your custom pack does not appear

Check the app name and version, then the import route, folder depth and config-to-audio filenames. A pack can contain valid audio while its configuration points somewhere else. Once it appears, check the keys you assigned and the segment lengths at a low playback level. Include Space, Enter and other keys you use; a successful import alone does not prove that every key is mapped.

For an unresolved error, give that app’s support channel your operating system, app version, pack format, folder structure and exact error. Keep private recordings and typed text out of public reports. These checks narrow the problem; they do not guarantee a fix for every import failure.

Klakk: choose from the included packs

The website Mac 1.4.1/build 23 and Windows 1.4.1 editions of Klakk provide 14 bundled packs. They do not offer a supported interface for importing your own WAV or MP3 file, importing Mechvibes packs or editing per-key mappings. Modifying the app’s installed resource directory is not a supported import workflow.

If you prefer included sounds, preview all 14 in the browser and use the pack-selection guide to compare them. The browser preview responds inside that page; use the installed app to evaluate typing in your usual desktop applications.

The website Mac edition supports macOS 14 or later, on Apple silicon and Intel. The Windows edition supports Windows 10/11, with native x64 and ARM64 builds. The trial starts at first launch and lasts three days. Continuing costs US$4.49 once per platform, plus applicable tax. Website Mac, Windows and App Store licences are separate.

Klakk processes keyboard events and codes locally, without uploading typed text or raw keystrokes. Usage analytics and trial/licensing communication still occur. The Mac edition also has settings telemetry; see the Mac privacy policy and Windows privacy policy. If custom recordings are essential to your choice, start with an app that supports that requirement.

Compare Mac keyboard-sound apps · Compare Windows apps · Download Klakk’s website editions

Download Klakk

For macOS and Windows. Try all 14 sound packs free for 3 days.

Preview all 14 sounds before downloading →

Keep exploring