Skip to content
Petal

FixesMac7 min read

VoiceInk not pasting or pasting the old clipboard: fixes

VoiceInk not pasting? Click the field first, set Paste Method to AppleScript, raise the Restore Delay, and reset Accessibility with tccutil after rebuilds.

Published by Optimal Apps, the maker of Petal.

On this page

VoiceInk not pasting your text? The transcript usually exists, and only the paste step failed. Click into the target field before you record, confirm VoiceInk has Accessibility access, then open Settings > Pasting and change Paste Method from Default to AppleScript. If VoiceInk pastes your old clipboard instead, raise the Restore Delay in the same pane. If the Accessibility switch is on but nothing works after a rebuild, reset the grant with tccutil.

The steps below follow VoiceInk's own clipboard documentation and two GitHub issues on the VoiceInk repository. Each fix lists the cause, so you can skip the ones that do not match your problem.

VoiceInk not pasting: quick-fix checklist

What you see Likely cause Fix
Transcript appears in History, nothing pastes No focused field, or the paste keystroke is blocked Click the field first, then set Paste Method to AppleScript
Old clipboard text pastes Clipboard restored before the app read it Raise Settings > Pasting > Restore Delay
Your clipboard is replaced by the transcript Keep Clipboard Content is off Turn on Keep Clipboard Content
Accessibility is on, still no paste Grant does not match the current code signature tccutil reset Accessibility com.prakashjoshipax.VoiceInk, relaunch, grant again
Fails only in Chrome, Brave, or other Chromium web fields Known intermittent issue (#1000) Update, then try the Direct Typing method
Fails with a non-US keyboard layout Simulated Command-V maps to the wrong key Keep Paste Method on AppleScript
Nothing pastes in one mode only The mode does not use Paste output Check the mode's output setting

Why VoiceInk is not pasting

VoiceInk, like most Mac dictation apps, does not type into other apps directly. It puts the transcript on the clipboard and sends a paste command to the front app. That needs three things to be true at the same time:

  1. A text field has keyboard focus when the transcript is ready.
  2. macOS allows VoiceInk to send input to other apps (Accessibility).
  3. The target app reads the clipboard before VoiceInk restores your old content.

When one of these fails, you get either no text or the wrong text. The fixes below map to each point.

Step 1: Confirm the mode pastes

VoiceInk's documentation says some outputs do not paste. Respond and Custom Command outputs deliver the result elsewhere, and imported files stay in the Transcribe queue and History.

  1. Open VoiceInk and check which mode is active.
  2. Confirm the mode uses Paste output.
  3. Open History and confirm the transcript exists. If it does, copy it from there so you do not lose it.

If the transcript is not in History, the problem is transcription, not paste. See VoiceInk not transcribing instead.

Step 2: Click the field before you record

VoiceInk pastes into whatever has focus when the transcript is ready. If you click elsewhere, switch apps, or a notification takes focus during processing, the paste goes nowhere.

  1. Click inside the text field.
  2. Start the recording.
  3. Stay in the field until the text appears.

Test in a simple app such as TextEdit or Notes first. If it works there, the problem is the target app, not VoiceInk.

Step 3: Check Accessibility access

macOS blocks simulated keystrokes from apps that do not have Accessibility access.

  1. Open System Settings > Privacy & Security > Accessibility.
  2. Find VoiceInk in the list and make sure the switch is on.
  3. If it is already on, turn it off and on again.
  4. Quit VoiceInk completely and open it again. VoiceInk's docs say to restart after permission changes.

If the switch is on and paste still fails in every app, go to Step 6.

Step 4: Set Paste Method to AppleScript

This is VoiceInk's main fix for "text is transcribed but nothing pastes".

  1. Open VoiceInk Settings > Pasting.
  2. Change Paste Method from Default to AppleScript.
  3. Test again in TextEdit, then in the target app.

Why it works: the Default method posts a Command-V keystroke. Some apps, and some custom keyboard layouts, do not treat that keystroke as a paste. The AppleScript method sends the paste a different way. VoiceInk's docs say to keep AppleScript on if you use a custom keyboard layout.

Step 5: Raise the Restore Delay when old clipboard text pastes

This is the most common "VoiceInk pastes the wrong thing" report.

  1. Open Settings > Pasting.
  2. Keep Keep Clipboard Content on.
  3. Raise Restore Delay. VoiceInk's docs give the default as 2 seconds and the range as 250 ms to 5 seconds.
  4. Test in the app that pasted the old content.

Why it works: with Keep Clipboard Content on, VoiceInk saves your clipboard, puts the transcript there, pastes, and then puts the old content back after the delay. A slow app, a busy web page, or a remote desktop can read the clipboard after the restore. It then pastes your old content. A longer delay gives the app more time.

If the opposite happens and your clipboard always holds the last transcript, turn Keep Clipboard Content on.

Step 6: Reset Accessibility with tccutil after a rebuild or reinstall

This fix matters if you build VoiceInk from source, switch between a source build and the paid build, or move the app.

GitHub issue #530 on the VoiceInk repository explains the cause: macOS ties Accessibility and Screen Recording grants to the app's code signature. A new build has a new signature, so the old grant no longer matches. System Settings can still show the switch as on, but macOS treats the app as a different app.

  1. Quit VoiceInk.
  2. Open Terminal and run:
tccutil reset Accessibility com.prakashjoshipax.VoiceInk
tccutil reset ScreenCapture com.prakashjoshipax.VoiceInk
  1. Open VoiceInk again.
  2. Grant Accessibility (and Screen Recording, if you use it) when macOS asks.
  3. Restart VoiceInk once more and test.

The same signature rule applies to all Mac apps. For more detail, see Accessibility permission not working after an app update.

Step 7: Chrome, Brave, and other Chromium web fields

GitHub issue #1000 on the VoiceInk repository, "Paste into web page fields (Chromium browsers) fails intermittently", describes a specific pattern:

  • The first dictation into a web field usually works.
  • Later dictations into the same kind of field silently do nothing.
  • A manual Command-V at that moment works, so the clipboard holds the right text.
  • Native apps and Electron apps are not affected.

Reports cover Brave, Google Chrome, and Helium. The root cause is not confirmed in the thread. The maintainer recommended updating to build 2.22 or later and switching to the Direct Typing paste method until Chromium ships a fix. Two users in the thread reported that Direct Typing works in Chrome and Helium.

  1. Update VoiceInk to the latest version.
  2. Open Settings > Pasting.
  3. Set Paste Method to Direct Typing, if your version has it.
  4. Test in the web field.

When Direct Typing is not available, press Command-V yourself after the dictation. The transcript is still on the clipboard until the restore delay ends.

Step 8: Fix extra or missing spaces

If the paste works but spacing is wrong, VoiceInk's docs point to AI Models > gear > Transcription > Add Space After Paste. Change the setting and test again.

If nothing works

Collect these details and open an issue on the VoiceInk GitHub repository or contact VoiceInk support:

  • Your macOS version and VoiceInk version.
  • Whether you use a source build or the paid build.
  • The target app and its version.
  • The Paste Method you tested.
  • Whether the transcript appears in History.

A free alternative: Petal for macOS

If you want a dictation app that pastes the same way in native, Electron, and web apps without paste-method settings, Petal for macOS is worth a test. It is free and open source (MIT), and it runs speech models on your Mac.

What Petal does differently on the paste step:

  • Restore delay built for slow apps. Petal puts the transcript on the clipboard, waits for you to release the shortcut keys, sends Command-V, and restores your old clipboard 700 ms later. The delay exists because Electron apps such as VS Code read the clipboard late.
  • No overwrite of new copies. If you copy something new during that 700 ms, Petal keeps your new copy and skips the restore.
  • A clear fallback. If Petal does not have Accessibility access, it copies the transcript to the clipboard and tells you to turn on Accessibility. The text is not lost.
  • Paste Last Transcription. You can set a shortcut in Settings > General that pastes your most recent transcript again.
  • Stable signature. Petal ships through GitHub Releases with Sparkle updates and a Developer ID signature, so an update does not break the Accessibility grant.

Petal is not a full replacement for every VoiceInk feature. Compare them in Petal vs VoiceInk, or read about other options in VoiceInk alternative.

Questions

Why does VoiceInk paste my old clipboard instead of the transcript?

VoiceInk puts the transcript on the clipboard, sends Command-V, and then puts your old clipboard back. If the target app reads the clipboard after the restore, it pastes the old content. Raise Settings > Pasting > Restore Delay to fix it.

What does the AppleScript paste method in VoiceInk do?

It sends the paste through AppleScript instead of the default simulated keystroke. VoiceInk recommends it when nothing pastes and when you use a custom keyboard layout.

VoiceInk shows Accessibility as on, but it still cannot paste. Why?

macOS ties the Accessibility grant to the app's code signature. After you rebuild VoiceInk from source or install a build with a different signature, the old grant no longer matches. Run tccutil reset Accessibility com.prakashjoshipax.VoiceInk, relaunch, and grant access again.

Why does VoiceInk fail only in Chrome or Brave web fields?

GitHub issue #1000 reports that later pastes into Chromium web fields can fail silently while native and Electron apps work. The maintainer suggested a recent build and the Direct Typing paste method as a workaround.

Is there a free alternative to VoiceInk that pastes into any app?

Petal for macOS is free and open source. It runs speech models on your Mac, pastes into the front app, and waits 700 ms before it restores your clipboard so slow apps get the transcript.

FixesMac

Mac dictation wrong language: how to fix it

Mac dictation wrong language? Add your language in Keyboard > Dictation, switch it while you dictate, check the input source, and finish the download.

FixesMac

Spokenly not working on Mac: how to fix it

Spokenly not working on Mac? Fix the microphone and Accessibility permissions, the shortcut, local model downloads, Local-only mode, and paste problems.