How to Refresh a Finder Window on the Macbook

Updated

Finder window on macOS

There is a real refresh command and it isn’t a keyboard shortcut — it’s AppleScript:

osascript -e 'tell application "Finder" to update POSIX file "/Volumes/share/folder"'

Finder’s own scripting dictionary defines update as “Update the display of the specified object(s) to match their on-disk representation”, which is exactly the missing refresh button. Everything else — navigating away and back, killall Finder — is a workaround for not knowing that command exists.

Where the refresh command actually is

Finder’s dictionary lives at /System/Library/CoreServices/Finder.app/Contents/Resources/Finder.sdef. The entry, verbatim:

<command name="update" code="fndrfupd"
  description="Update the display of the specified object(s) to match their on-disk representation">
  <direct-parameter type="specifier" description="the item to update"/>
  <parameter name="necessity" code="nec?" type="boolean" optional="yes"
    description="only update if necessary (i.e. a finder window is open). default is false"/>
  <parameter name="registering applications" code="reg?" type="boolean" optional="yes"
    description="register applications. default is true"/>
</command>

It runs clean against a real path:

$ mkdir -p /tmp/hwfinder
$ osascript -e 'tell application "Finder" to update POSIX file "/tmp/hwfinder"'
$ echo $?
0

Wrap it in a shell alias and you have the button macOS never shipped:

refresh() { osascript -e "tell application \"Finder\" to update POSIX file \"${1:-$PWD}\""; }

Relaunch Finder with killall Finder without losing your windows

I measured this in August 2026 with three Finder windows open. This is the log from the script I used, which also timed the relaunch:

$ pgrep -x Finder
1278
$ osascript -e 'tell application "Finder" to count Finder windows'
3

$ killall Finder

$ pgrep -x Finder
3652
relaunch_seconds=0.17

$ osascript -e 'tell application "Finder" to count Finder windows'
3

New PID, same three windows. Their targets and their pixel bounds came back identical:

before: /Users/[user]/Downloads/|94,289,1181,1095
after:  /Users/[user]/Downloads/|94,289,1181,1095

Finder persists window state in ~/Library/Preferences/com.apple.finder.plist and restores it on relaunch. What killall Finder does still do is send SIGTERM, which is not a clean quit — an in-flight Finder copy will be interrupted. Don’t run it while a progress bar is on screen. A mounted share belongs to the kernel rather than to Finder, so mount entries should outlive the relaunch; I did not confirm that part and you should not take it from me.

The navigation tricks, and the catch nobody mentions

These shortcuts are keyboard behaviour, so they need a human at the machine, and I could not drive them from a script.

Cmd+Up then Cmd+Down is Go > Enclosing Folder, then Open. It re-reads the directory because Finder builds a listing when it enters a folder. The catch: Cmd+Down opens the selected item, so if nothing is selected after you go up a level you end up stranded in the parent folder. That is why people report this one “not working”.

Cmd+[ then Cmd+] is Back then Forward. Same effect, no selection required, so it’s the one to use.

Cmd+Shift+A then Cmd+[ jumps to Applications, then jumps back. That is Back with a detour through a large folder, and there’s no reason to prefer it.

Why you usually don’t need any of this

On a local APFS volume Finder is driven by FSEvents and picks up changes on its own, which is why most people never notice the missing refresh button. The cases where you do need it are exactly the ones where FSEvents doesn’t reach you:

  • SMB and AFP shares — the server changed the folder, your Mac was never told.
  • Network volumes over a VPN, where notifications are dropped even when the mount is healthy.
  • Files written by another user or a background process on the same server.
  • FUSE-style mounts (sshfs, cloud drive clients), which vary wildly in whether they emit events at all.

For those, the AppleScript update above is the right tool: it targets one folder, it doesn’t disturb your other windows, and it doesn’t restart anything.

If Finder is genuinely stuck

Relaunching from the GUI does the same job as killall and is slightly gentler: hold Option and right-click the Finder icon in the Dock, then choose Relaunch. Use the Terminal form when you’re already in a Terminal:

$ killall Finder

If Finder doesn’t come back within a second or two, something bigger is wrong, and the next thing to check is whether a network mount is hung (mount | grep -E 'smbfs|nfs' and then umount -f the offender).

Photo of author
Sudhir P. founded HeatWare.com in 1999 and has built and operated it full-stack ever since; it is now used by more than 88,000 people. He writes here about the PostgreSQL, MySQL, Linux and DevOps work that keeps it running. Articles are rewritten only after the commands in them have actually been run, and the verification scripts are published alongside them so anyone can check the claims. Reach him at blog@heatware.net.