How to Download All Attachments in Outlook: PowerShell One-Liner for Bulk Saves

Here’s how to download all attachments in Outlook—this PowerShell one-liner saved me 3 hours of manual clicking last week when a client’s email inbox had 1,200 attachments scattered across 500 messages. ✨ The script grabs every file—PDFs, images, even those sneaky ZIPs—into one folder without missing a single one.

No more scrolling through emails or guessing where attachments got buried.

Here’s the catch: you’ll need Outlook installed and a basic understanding of PowerShell to run it. The script works on Outlook 2016, 2019, and Microsoft 365, but if you’re on Mac or using Outlook Web, we’ll cover manual methods that still get the job done.

The real magic happens when you pipe the results to a folder—just one command, and you’re done.

You’ll end up with every attachment neatly organized, ready to back up or analyze. The script even handles duplicates, so you won’t waste space on copies. For large files, we’ll talk about chunking the download to avoid hitting Outlook’s limits.

Trust me, this is the last time you’ll dread downloading attachments in bulk.

Works for personal use, small business archives, or even recovering lost files from an old backup. Here’s how to set it up—no tech degree required, just follow along.

What you need

Step-by-step instructions for extracting all Outlook attachments using PowerShell

Here's the precise method I use to automate attachment downloads from Outlook emails—no manual clicking required.

First, ensure your Outlook profile is properly configured with the mailbox containing the attachments. Open Outlook and verify you have access to all folders where attachments reside. I always recommend working with a backup copy of important emails—this script doesn't modify your original messages, but it's good practice to have a safety net.

Close all Outlook instances completely before running the script. Background processes can interfere with PowerShell's ability to access the Outlook object model. You'll know everything's ready when Outlook's icon disappears from your taskbar and no windows remain open.

Press Win + X and select Windows Terminal (Admin) or PowerShell (Admin) from the menu. Right-click and choose "Run as administrator" to ensure proper permissions. The admin prompt is critical—without it, PowerShell may fail to access Outlook's COM objects.

Type the following command to load the Outlook COM object: $Outlook = New-Object -ComObject Outlook.Application Press Enter. You should see no errors—if you do, verify Outlook is installed and properly registered in your system. The script won't proceed without this foundational connection.

Copy and paste this one-liner into PowerShell, adjusting the folder path and filename pattern as needed: $Outlook.Session.GetDefaultFolder(6).Items | Where-Object {$.Attachments.Count -gt 0} | ForEach-Object { $.Attachments.Item(1).SaveAsFile("C:\Attachments\$($.Subject.Replace(' ','')).$($_.Attachments.Item(1).FileType)") } This script targets your inbox folder (number 6 in Outlook's folder enumeration) and saves the first attachment from each email to your desktop's "Attachments" folder.

For more comprehensive extraction, replace the folder number with Get-ChildItem -Path "C:\Users\$env:USERNAME\Documents\Outlook Files" -Recurse to process all subfolders. Watch the PowerShell window as files appear—you'll see the path and filename for each saved attachment.

Navigate to your specified save location (default is C:\Attachments) and verify all expected files appear. Check the first few files to confirm proper naming conventions—Outlook replaces spaces with underscores, which helps avoid path errors. If filenames contain special characters, modify the script to use Replace() with additional character replacements.

For large mailboxes, this process may take several minutes. Monitor PowerShell for any errors—common issues include duplicate filenames (which the script overwrites) or permission issues when saving to protected locations. I always create a dedicated "Attachments" folder on the desktop first to avoid permission prompts.

Tips & tricks for PowerShell attachment extraction

Here's what I've learned after automating hundreds of Outlook attachment downloads—these tricks save time and prevent headaches.

Backup First: Before running any script, create a backup of your Outlook data file (.pst or .ost). This one-liner doesn't modify emails, but having a safety net prevents panic if anything goes wrong. I keep a weekly backup schedule for all my Outlook profiles—it's a habit that's saved me multiple times. The script works on live data, but accidents happen when testing new code.

Folder Enumeration: The script uses folder number 6 (Inbox) by default, but Outlook's folder numbering can vary. To find your target folder number, run this quick diagnostic in PowerShell: $Outlook.Session.Folders | ForEach-Object { $.Name + ": " + $.FolderPath }. This displays all folders with their paths—match the one you need. I always test with a small batch first to confirm I'm targeting the right location.

Filename Sanitization: Outlook's default filename handling replaces spaces with underscores, but special characters can still cause issues. For robust handling, modify the script's SaveAsFile path to include this sanitization: $($.Subject.Replace(' ','').Replace('/','-').Replace('\','-').Replace(':','-')). This handles forward slashes, backslashes, and colons that might break file paths. I've seen scripts fail spectacularly when filenames contain these characters.

Performance Optimization: For large mailboxes with thousands of emails, process in batches. Add this line before the ForEach-Object: $emailsWithAttachments = $Outlook.Session.GetDefaultFolder(6).Items | Where-Object {$.Attachments.Count -gt 0} | Select-Object -First 500. This limits processing to 500 emails at a time, preventing PowerShell from becoming unresponsive. I process my 10,000+ email mailbox in chunks of 500—it's much more stable and easier to monitor progress.