How to Leave a Long Export, Render, Upload or File Transfer Running on a Mac Safely: Screen On, Progress Visible, Keyboard Locked

Every Mac owner has a version of this moment. The Final Cut export says 41 minutes. The Xcode archive is uploading to App Store Connect. The 200 GB photo library is copying to the new drive, or Handbrake is grinding through a season of home video. You need to leave the desk, and three worries arrive at once: will the screen sleep and take the job with it, will someone touch the keyboard and cancel it, and will you be able to tell from across the room whether it is still going? This post is about leaving a long export, render, upload or transfer running on a Mac safely, what macOS does and does not do for you, and where a $10 keyboard lock fits.

First, separate the three worries

• Will the job keep running? Usually yes. Modern macOS keeps CPU work going when the display sleeps, and apps doing exports or uploads typically ask the system not to idle-sleep while they work. The real danger is the lid: closing a MacBook without an external display attached puts it to sleep, and most exports pause or fail. Keep the lid open, or use clamshell mode with a monitor and power.
• Will someone interfere? This is the worry macOS handles worst. Anyone who walks past an unlocked Mac can press Escape in a dialog, close the wrong window, or lean on the keyboard. The built-in lock screen stops that but blanks the display.
• Can I see progress at a glance? Only if the screen is on and the progress window is visible. A locked, sleeping Mac tells you nothing until you wake it and type a password, by which point you may have interrupted the very thing you came to check.

The second and third worries pull in opposite directions: the way to stop interference is to lock, and locking hides the progress bar. That gap is the whole reason a tool like VibeLock exists.

What macOS gives you out of the box

You have three honest options without installing anything. The first is the lock screen (⌃⌘Q): secure, but the display goes dark, and if someone wakes it they see a login prompt rather than your export. The second is a caffeinate-style setting that keeps the display awake while the job runs; good for visibility, zero protection against a stray hand. The third is to simply trust the room, which works until the one time it does not.

None of them give you the combination most people actually want for a long job: screen on, progress visible, keyboard and trackpad dead to everyone but you. Our post on locking the keyboard while keeping the screen on goes through the built-in alternatives in more depth; the short version is that macOS does not have a watch-only mode.

The watch-only setup for a long job

VibeLock sorts every app on your Mac into one of three buckets while it is engaged. Apps marked Visible While Locked stay on screen but every keystroke, click and scroll aimed at them is swallowed. Apps marked Accessible While Locked can still be used. Everything else is hidden behind an opaque backdrop and kept hidden. For a render or upload, the recipe is:

1. Start the job and get its progress window where you want it on screen. For a Finder copy that is the copy dialog; for Final Cut or Compressor it is the export progress; for Xcode it is the Organizer upload sheet; for a terminal command it is the terminal.
2. From the VibeLock menu bar icon, mark that app Visible While Locked. Terminal, iTerm2, Warp, Ghostty, kitty, Alacritty, WezTerm, Claude desktop, ChatGPT/Codex and VS Code are pre-allowed; any other app you toggle on from the same menu.
3. Leave the Accessible list empty. For a job you merely want to watch, watch-only is the safe baseline. The only reason to make an app accessible is if someone else needs to click something while you are away, which is a different scenario covered in letting a colleague approve a prompt without unlocking.
4. Lock. VibeLock holds the display awake while locked, so the progress bar stays lit for as long as you are gone, and a glance from the door tells you whether the job is at 60% or finished.
5. Come back and unlock with Touch ID, or your macOS login password typed into VibeLock, verified locally against your account.

What a passer-by can and cannot do

While locked, a system-wide event tap swallows keys, clicks, scrolls and gestures, so leaning on the keyboard, pressing Escape in the export dialog, or clicking Cancel does nothing. Spotlight (⌘Space), Force Quit (⌘⌥Esc) and ⌘Q are blocked system-wide, VibeLock refuses to quit, and a watchdog re-arms the input firewall if macOS ever disables it. Fullscreen windows of hidden apps stay where they are but are covered by an opaque shield if anyone swipes to them, and your visible apps work across all Spaces and displays.

What it cannot do is stop someone unplugging the drive, closing the lid, or pulling the power. Those are physical acts, and no software lock prevents them. If the job depends on a cable, make sure the cable is out of the way; if it depends on the lid being open, say so to whoever shares the space.

Honest trade-offs

• It does not keep a MacBook awake with the lid closed. VibeLock holds the display awake. It is not a substitute for a powered clamshell setup, and it does not change what your export app does on sleep.
• Watch-only means you cannot nudge the job either. If the upload throws a dialog that needs a click, it will sit there until you unlock. For a job that may need babysitting, mark that one app Accessible and accept the narrower protection, or stay nearby.
• It is a lock, not a kiosk. It needs you, or your Touch ID, to unlock. If the plan is to leave a Mac unattended for days, the macOS lock screen plus a scheduled job and a notification is the better design; VibeLock is for the hours, not the week.
• Accessibility permission. Input blocking requires the macOS Accessibility permission, which VibeLock asks for on first lock. That is the only permission it needs; it makes no network calls and has no accounts.

Three real scenarios

The overnight video export. Export running, Final Cut marked visible, lock, go to bed. In the morning the screen shows either the finished timeline or the error, and nobody in the house has accidentally dragged a clip while looking for the light switch. If you would rather not have the display on all night, this is the case for the plain lock screen instead: you are not going to glance at it, so visibility buys you nothing.

The App Store upload at the office. Xcode's Organizer is uploading a build and you are called into a meeting. Mark Xcode visible, lock, go. Colleagues can see it is uploading and leave it alone; nobody can hit Cancel; you come back to a finished upload or a clear error. This is the same reasoning behind leaving an agent run visible, which our Claude Code post covers.

The big copy to a new drive. A Finder copy of a photo library can take an hour, and the copy dialog is tiny and easy to close by accident. Mark Finder visible, lock. Keep the drive's cable where no foot will find it.

Summary

For a long export, render, upload or transfer, the risks are sleep, stray input and blind waiting. Sleep is a lid and power problem that no lock fixes. Stray input and blind waiting are the same problem seen from two sides, and VibeLock solves both at once: screen on, progress visible, every key and click blocked, unlock with Touch ID. It is a 2 MB native menu bar app for macOS 13 or later, signed and notarized by Apple, and it costs $10 once.