Old downloads, old project files, and old screenshots pile up quietly. Instead of manually hunting for what’s safe to move, this script does it by date — automatically, and safely (nothing gets deleted, just moved).
set targetFolder to choose folder with prompt "Choose a folder to archive old files from:"
set daysOld to 90
set cutoffDate to (current date) - (daysOld * days)
tell application "Finder"
if not (exists folder "Archive" of targetFolder) then
make new folder at targetFolder with properties {name:"Archive"}
end if
set archiveFolder to folder "Archive" of targetFolder
repeat with aFile in (get files of targetFolder)
if modification date of aFile < cutoffDate then
move aFile to archiveFolder
end if
end repeat
end tell
daysOld is 90 by default (files older than 90 days get archived)Nothing is deleted — files just move into a subfolder, so it’s easy to check or undo.
Want 30 days instead of 90? Just change one line:
set daysOld to 30
modification date catches files that were edited recently even if created long ago. If you’d rather archive based on when a file was first created:
if creation date of aFile < cutoffDate then
move aFile to archiveFolder
end if
To only archive, say, PDFs and images and leave everything else alone:
set targetFolder to choose folder with prompt "Choose a folder to archive old files from:"
set daysOld to 90
set cutoffDate to (current date) - (daysOld * days)
set archiveTypes to {"pdf", "png", "jpg", "jpeg"}
tell application "Finder"
if not (exists folder "Archive" of targetFolder) then
make new folder at targetFolder with properties {name:"Archive"}
end if
set archiveFolder to folder "Archive" of targetFolder
repeat with aFile in (get files of targetFolder)
try
set fileExtension to name extension of aFile
if (modification date of aFile < cutoffDate) and (fileExtension is in archiveTypes) then
move aFile to archiveFolder
end if
end try
end repeat
end tell
Your folder now self-cleans on a schedule, no manual runs needed.
choose folderBecause this script uses choose folder, it can’t run fully unattended without modification — the picker needs a click. For a scheduled version, hardcode the path instead:
set targetFolder to (POSIX file "/Users/yourname/Downloads") as alias
Replace the path and username with your own. Find your exact path by right-clicking a folder in Finder while holding Option, then choosing Copy “FolderName” as Pathname.
“Finder got an error: Can’t get folder Archive”
This shouldn’t happen since the script checks exists first — but if it does, the folder name may have trailing spaces or hidden characters. Delete it and let the script recreate it.
Files aren’t being archived that should be
Check daysOld — and remember modification date updates every time a file is opened and re-saved, so a file you think is “old” might have been touched more recently than expected.
Scriptly includes this as a built-in template — no setup required, plus AI generation if you want custom archiving rules described in plain English.
Every AppleScript beginner hits the same handful of errors. Here’s what each one actually means and how to fix it — not just the workaround, but the reason it happens.
What it means: macOS requires explicit permission before one app (like Script Editor) can control another (like Mail or Finder). This is a privacy protection, not a bug.
Fix:
If you exported your script as a standalone app, look for that app’s name in the Automation list instead.
What it means: The script is trying to reference a file or folder that doesn’t exist — either it was moved, renamed, or the path/name in your script has a typo.
Fix: Double-check spelling and capitalization exactly. AppleScript is picky about exact names. Consider wrapping risky operations in a check:
tell application "Finder"
if exists file "report.pdf" of desktop then
-- safe to proceed
else
display dialog "File not found."
end if
end tell
What it means: This is AppleScript’s version of a typo error — a missing end tell, a stray character, or mismatched quotes.
Fix: Check that every tell, if, and repeat has its matching end tell, end if, or end repeat. Script Editor’s syntax highlighting helps — unmatched blocks often show up in a different color or with obvious indentation breaks.
Common culprit — smart quotes. If you copy code from a website or Word doc, curly quotes (" ") can sneak in instead of straight quotes ("), and AppleScript won’t recognize them:
-- Broken (smart quotes):
display dialog “Hello”
-- Fixed (straight quotes):
display dialog "Hello"
What it means: Your script is trying to control an app that isn’t currently open.
Fix: Add activate before your commands, or check is running first:
tell application "Mail"
if not running then
activate
delay 2 -- give it a moment to launch
end if
-- your commands here
end tell
What it means: You’re trying to change something that’s either read-only, or the object reference is wrong.
Fix: Common cause is naming collisions — trying to rename a file to a name that already exists in that folder:
tell application "Finder"
if not (exists file "newname.txt" of targetFolder) then
set name of theFile to "newname.txt"
else
display dialog "A file with that name already exists."
end if
end tell
What it means: Usually your filtering condition (an if, or a whose clause) didn’t match anything — not an error, just zero results.
Fix: Add a quick debug line to check what’s actually being found:
set matchingItems to (every file of targetFolder whose name contains "invoice")
display dialog "Found: " & (count of matchingItems)
If the count is 0, your search text or condition needs adjusting.
What it means: The app you’re controlling is waiting on something — often a dialog box hidden behind another window, or a slow operation (like a large do shell script command).
Fix: Add an explicit timeout around the risky section:
with timeout of 30 seconds
tell application "Mail"
-- slow operation here
end tell
end timeout
Post the exact error message on r/applescript — the community is fast and genuinely helpful with beginner questions.
Or skip the debugging entirely: Scriptly generates tested, working AppleScript from a plain-English description, so you’re starting from working code instead of fixing broken code.
AppleScript is old. It first shipped in 1993. Apple’s marketing energy has gone almost entirely into Shortcuts for over half a decade. And yet — professionals doing real automation work on Mac still reach for it constantly. Here’s why.
Shortcuts is great for iOS-style automations: toggling settings, quick text transforms, simple app actions. But most professional Mac software — Adobe Creative Suite, Microsoft Excel, FileMaker, DEVONthink, BBEdit, and dozens of others — exposes deep automation through Apple Events, which is what AppleScript talks to directly.
If you need to loop through 400 InDesign pages, batch-process Excel spreadsheets, or script Finder operations with real conditional logic, AppleScript (or its JavaScript cousin, JXA) is usually still the only option.
A widely upvoted post on r/applescript put it well: AppleScript “remains remarkably stable over the years.” Scripts written a decade ago still run today with little to no modification. For production workflows — the kind studios and agencies depend on daily — that stability is worth more than new features.
There’s periodic anxiety in the community about AppleScript’s long-term future, but Apple has kept it alive as the underlying automation layer for macOS for over 30 years, through OS 9, Mac OS X, and Apple Silicon. Even Shortcuts on Mac runs many of its actions through the same Apple Events system AppleScript uses.
AppleScript’s English-like syntax is approachable in theory (“tell application… to…”), but in practice, remembering exact command names, correct capitalization, and app-specific dictionaries is where beginners get stuck. That’s a real, valid criticism — but it’s a tooling problem, not a reason the language itself is obsolete.
This is exactly the gap apps like Scriptly exist to close: describe a task in plain English, get working AppleScript back, powered by on-device AI so nothing leaves your Mac. You get AppleScript’s real power over apps, without needing to memorize its dictionaries.
To be fair, Shortcuts is genuinely better for:
For anything involving Mail, Finder batch operations, or professional creative/office apps at scale, AppleScript still wins.
AppleScript isn’t legacy cruft — it’s infrastructure. It’s the layer that lets Mac apps talk to each other, and there’s no real replacement for the depth of control it offers on macOS. The barrier has always been syntax, not usefulness, and that barrier is finally coming down.
No theory, no setup — just ten working scripts. Paste any of these into Script Editor (Applications → Utilities) and click Run.
tell application "Finder"
empty trash
end tell
display notification "Backup finished!" with title "Scriptly" sound name "Glass"
Useful at the end of longer scripts so you know when they’re done.
tell application "System Events"
set frontApp to name of first application process whose frontmost is true
end tell
display dialog "You're using: " & frontApp
set targetFolder to choose folder
tell application "Finder"
set fileCount to count of (files of targetFolder)
end tell
display dialog "That folder has " & fileCount & " files."
Handy before a screen recording or presentation:
set keepOpen to {"Finder", "Script Editor"}
tell application "System Events"
set runningApps to name of every process whose background only is false
end tell
repeat with appName in runningApps
if appName is not in keepOpen then
try
tell application appName to quit
end try
end if
end repeat
set sourceFolder to choose folder with prompt "Folder to back up:"
set destFolder to choose folder with prompt "Where to back it up:"
set sourcePath to POSIX path of sourceFolder
set destPath to POSIX path of destFolder
do shell script "rsync -av " & quoted form of sourcePath & " " & quoted form of destPath
display notification "Backup complete" with title "Scriptly"
rsync only copies what’s changed, so re-running this is fast after the first backup.
set theFile to choose file with prompt "Pick a text file:"
set fileContent to read theFile as «class utf8»
set upperContent to do shell script "echo " & quoted form of fileContent & " | tr '[:lower:]' '[:upper:]'"
set theResult to open for access theFile with write permission
set eof of theResult to 0
write upperContent to theResult
close access theResult
tell application "System Events"
tell appearance preferences
set dark mode to not dark mode
end tell
end tell
tell application "Finder"
eject (every disk whose ejectable is true)
end tell
Great as the last step before shutting down for the day.
set todayDate to (current date)
set dateString to (year of todayDate as string) & "-" & my padded(month of todayDate as integer) & "-" & my padded(day of todayDate)
tell application "Finder"
make new folder at desktop with properties {name:"Notes-" & dateString}
end tell
on padded(n)
if n < 10 then
return "0" & n
else
return (n as string)
end if
end padded
Good for daily journaling folders, scanned receipts, or a “today’s downloads” staging area.
For any script above:
These ten cover the basics. Scriptly has 100+ ready-made templates across email, files, calendar, Slack, and GitHub — plus AI generation for anything not already covered.
Everyone’s Downloads folder looks the same: a graveyard of PDFs, screenshots, installers, and random zip files. Here’s a script that sorts it into subfolders by file type — safely, and re-runnable any time.
tell application "Finder"
set downloadsFolder to (path to downloads folder) as alias
set folderNames to {"Images", "Documents", "Videos", "Archives"}
repeat with aName in folderNames
if not (exists folder aName of downloadsFolder) then
make new folder at downloadsFolder with properties {name:aName}
end if
end repeat
set imageTypes to {"png", "jpg", "jpeg", "gif", "heic"}
set docTypes to {"pdf", "doc", "docx", "txt", "xlsx", "pages"}
set videoTypes to {"mp4", "mov", "mkv"}
set archiveTypes to {"zip", "dmg"}
repeat with aFile in (get files of downloadsFolder)
try
set fileExtension to name extension of aFile
if fileExtension is in imageTypes then
move aFile to folder "Images" of downloadsFolder
else if fileExtension is in docTypes then
move aFile to folder "Documents" of downloadsFolder
else if fileExtension is in videoTypes then
move aFile to folder "Videos" of downloadsFolder
else if fileExtension is in archiveTypes then
move aFile to folder "Archives" of downloadsFolder
end if
end try
end repeat
end tell
try so one problem file (like something with no extension) doesn’t stop the whole scriptAdd more categories — for example, app installers:
set folderNames to {"Images", "Documents", "Videos", "Archives", "Installers"}
…and add a matching type list plus else if branch:
set installerTypes to {"dmg", "pkg"}
(Note: if you add “dmg” here, remove it from archiveTypes so it doesn’t get checked twice.)
Skip files still downloading — Safari names in-progress downloads something.download. This script already ignores them since .download isn’t in any of the type lists.
Rather than remembering to run this manually:
Now your Downloads folder tidies itself every night.
“Finder got an error: doesn’t understand the ‘move’ message” This usually means the file was already moved or renamed by something else mid-script (like Spotlight temporarily locking a file). Just run the script again.
Files aren’t moving
Check the extension actually matches what’s in your list — extensions are case-sensitive in some checks; consider lowercasing with fileExtension as lowercase for stricter matching, though name extension already normalizes case in most cases.
A folder named “Images” already exists with different contents
The script checks with exists folder... of downloadsFolder and won’t overwrite it — it’ll just use the existing folder as the destination.
Scriptly has this exact template built in, ready to run, plus 100+ others for files, email, and calendars.
Camera exports named IMG_4821.jpg, IMG_4822.jpg… are useless for finding anything later. Here are two AppleScript approaches to fix that — no third-party app needed.
set targetFolder to choose folder with prompt "Select folder of photos to rename:"
tell application "Finder"
set fileList to sort (get files of targetFolder) by name
end tell
set counter to 1
repeat with aFile in fileList
tell application "Finder"
set fileExtension to name extension of aFile
set newName to "Vacation-" & my zeroPad(counter) & "." & fileExtension
set name of aFile to newName
end tell
set counter to counter + 1
end repeat
on zeroPad(n)
if n < 10 then
return "0" & n
else
return (n as string)
end if
end zeroPad
What it does: Asks you to pick a folder, sorts the files by their current name, then renames each one to Vacation-01.jpg, Vacation-02.jpg, and so on.
To customize: Change "Vacation-" to whatever prefix you want (e.g. "Wedding-", "Trip2026-").
This is more useful for actually organizing a photo library — it renames files using the date the photo was modified/created, so they sort chronologically.
set targetFolder to choose folder with prompt "Select folder of photos to rename:"
tell application "Finder"
set fileList to get files of targetFolder
repeat with aFile in fileList
set fileExtension to name extension of aFile
set fileDate to creation date of aFile
set dateString to (year of fileDate as string) & "-" & my padded(month of fileDate as integer) & "-" & my padded(day of fileDate)
set baseName to dateString & "-" & (name of aFile)
set name of aFile to baseName
end repeat
end tell
on padded(n)
if n < 10 then
return "0" & n
else
return (n as string)
end if
end padded
What it does: Prefixes each filename with its creation date, e.g. IMG_4821.jpg becomes 2026-08-20-IMG_4821.jpg. This keeps the original name (so nothing is lost) while making files sort by date in Finder.
Tip: Always test on a copy of your photos first. Renaming is easy to do but tedious to undo by hand.
“Finder got an error: Can’t set name of file to…“ Usually means a file with that new name already exists in the folder — two photos with the same creation date and original name will collide. Add a counter suffix if this happens often.
Script skips some files
Non-image files in the folder (like .DS_Store) will still get renamed by these scripts since they operate on every file. Add a check like if fileExtension is in {"jpg", "jpeg", "png", "heic"} then around the rename logic to only touch photos.
Updated version with that filter:
set targetFolder to choose folder with prompt "Select folder of photos to rename:"
set photoTypes to {"jpg", "jpeg", "png", "heic"}
tell application "Finder"
set fileList to get files of targetFolder
repeat with aFile in fileList
set fileExtension to name extension of aFile
if fileExtension is in photoTypes then
set fileDate to creation date of aFile
set dateString to (year of fileDate as string) & "-" & my padded(month of fileDate as integer) & "-" & my padded(day of fileDate)
set name of aFile to (dateString & "-" & (name of aFile))
end if
end repeat
end tell
on padded(n)
if n < 10 then
return "0" & n
else
return (n as string)
end if
end padded
Scriptly has a ready-made photo batch-rename template, plus AI generation if you want a custom naming pattern — just describe it in plain English.
The problem: Invoices, newsletters, and work emails all land in one inbox. Sorting them manually eats up real time every week.
The fix: A short AppleScript that automatically moves emails into folders based on who sent them — running in seconds instead of minutes.
This works with Apple Mail (not Gmail’s web interface, though Mail can connect to Gmail accounts). You’ll need:
To create a mailbox: open Mail → Mailbox menu → New Mailbox → name it (e.g. “Billing”) → choose “On My Mac” or your account.
tell application "Mail"
set sourceMailbox to inbox
set targetMailbox to mailbox "Billing"
set matchingMessages to (every message of sourceMailbox whose sender contains "stripe.com")
repeat with aMessage in matchingMessages
move aMessage to targetMailbox
end repeat
end tell
What this does: Looks at every message in your inbox, finds ones where the sender’s address contains “stripe.com”, and moves each one into your “Billing” mailbox.
"Billing" to your actual mailbox name"stripe.com" to the sender you want to filter (a company domain, or a full email address)Your matching emails move instantly.
Want to catch several senders at once? Use or:
tell application "Mail"
set targetMailbox to mailbox "Billing"
set matchingMessages to (every message of inbox whose sender contains "stripe.com" or sender contains "paypal.com")
repeat with aMessage in matchingMessages
move aMessage to targetMailbox
end repeat
end tell
tell application "Mail"
set targetMailbox to mailbox "Receipts"
set matchingMessages to (every message of inbox whose subject contains "Receipt")
repeat with aMessage in matchingMessages
move aMessage to targetMailbox
end repeat
end tell
To run this every morning without opening Script Editor:
EmailOrganizer.appNow your inbox files itself before you’ve had coffee.
“Mail got an error: Can’t get mailbox ‘Billing’“ The mailbox doesn’t exist yet, or the name doesn’t match exactly (check capitalization). Create it via Mail → Mailbox → New Mailbox first.
Nothing happens, no error
Your filter condition didn’t match anything — double check the sender/subject text is exactly right (it’s case-sensitive for exact matches, though contains is fairly forgiving with partial text).
“Not authorized to send Apple events to Mail” Go to System Settings → Privacy & Security → Automation, find Script Editor (or your exported app), and enable Mail.
Scriptly includes ready-made email templates (auto-archive, flag, forward, and more) — or describe your rule in plain English and it writes the script for you.
If the word “AppleScript” makes you think of dense code and hours of frustration, this post is for you. AppleScript is actually one of the friendliest programming languages ever made — it reads almost like plain English on purpose.
By the end of this post you’ll understand what AppleScript is, how it works, and you’ll have written a real script yourself.
AppleScript is a scripting language built into every Mac. It lets you tell apps what to do — move files, send emails, resize windows, rename photos — without clicking through menus manually.
Instead of writing:
function moveFile(file, folder) { ... }
AppleScript reads like this:
tell application "Finder"
move file "report.pdf" to folder "Documents"
end tell
That’s it. That’s a real, working line of AppleScript. tell application "X" is how almost every script starts — you’re telling an app what you want it to do.
tell blocksEverything happens inside a tell block, which targets one app at a time:
tell application "Finder"
-- commands for Finder go here
end tell
Variables store information you want to reuse, using set:
set myName to "Luke"
display dialog "Hello, " & myName
& joins text together. That’s basically the whole language — apps, commands, and variables.
Every Mac has Script Editor built in (Applications → Utilities → Script Editor). It’s where you write, test, and run AppleScript.
That permission prompt is normal — macOS wants to confirm you trust the script to control apps like Finder or Mail.
Let’s write something actually useful: a script that shows a popup with today’s date.
set todayDate to current date
display dialog "Today is " & todayDate buttons {"OK"} default button "OK"
Paste that into Script Editor and hit Run. You should see a popup with today’s date. Congratulations — you just wrote and ran AppleScript.
Here’s a script that renames a file you choose:
set theFile to choose file with prompt "Pick a file to rename:"
tell application "Finder"
set name of theFile to "renamed-file.txt"
end tell
display dialog "Done! File renamed."
Notice the pattern:
choose file)Almost every useful AppleScript follows this same three-step shape.
Forgetting end tell — every tell application needs a matching end tell, or you’ll get a syntax error.
Typos in app names — tell application "finder" (lowercase) will fail. App names are case-sensitive: "Finder", "Mail", "Photos".
Running a script that needs a file/folder that doesn’t exist — if your script references a folder called “Archive” that you haven’t created yet, it’ll error out. Create it first, or add a check (we cover this in Fix Common AppleScript Errors).
Honestly, this is the part most beginners get stuck on — remembering exact syntax, app-specific commands, and correct capitalization. That’s exactly the problem Scriptly solves: describe what you want in plain English, and it generates working AppleScript for you, or pick from 100+ ready-made templates.
But understanding the basics above means you can actually read what Scriptly generates, tweak it, and troubleshoot it yourself — which is a genuinely useful skill.
Questions? The r/applescript community is active and helpful for beginners.
]]>