Windows' context menu still hides a small, decades‑old productivity trick that many users have overlooked: the classic
Send To submenu. Once a staple of Windows 95 and Windows XP workflows, it survives intact in Windows 11 — not as a flashy new feature, but as a tiny, extremely practical mechanism you can customize to speed file movement, automate batch processing, or open files in the exact tool you need. This article explains how Send To works today, shows concrete ways to bend it to your will, verifies the technical details against official documentation, and evaluates the benefits and risks of relying on this “forgotten” menu in modern Windows environments.
Background / Overview
The Send To context menu entry is populated from a simple per‑user folder named
SendTo. Windows exposes that folder via the shell alias shell:sendto, and every shortcut (.lnk), script, or program placed inside becomes an entry in the Send To submenu. That mapping is baked into Windows’ Known Folder system:
FOLDERID_SendTo has a default path of %APPDATA%\Microsoft\Windows\SendTo (a per‑user folder), and Windows has used this mechanism since the early shell days. This is why the same trick that worked in XP still works in Windows 11: the underlying shell hook was never removed.
Microsoft’s official guidance and community documentation confirm the behavior and location; community tutorials have long recommended using shell:sendto to manage those shortcuts. Practical how‑to guides from established Windows outlets describe the exact steps (Win+R → shell:sendto → add or remove shortcuts). These resources remain current for Windows 11.
How Send To actually works (technical fundamentals)
The SendTo folder and KnownFolder mapping
- Folder location: The Send To menu draws its entries from the per‑user SendTo folder: %APPDATA%\Microsoft\Windows\SendTo. Windows documents this as FOLDERID_SendTo in the Known FOLDERID list. Because it’s per‑user, you do not need administrative rights to add or remove entries for your account.
What you can put in the folder
- Shortcuts (.lnk) to folders (so right‑click → Send To copies/moves files to that folder)
- Shortcuts to programs or to wrapper scripts (so you can send files directly into an application or script)
- Batch scripts (.bat, .cmd), PowerShell scripts, or compiled utilities (you can place either the script itself or a shortcut to it)
- Special shell items (some legacy entries like Compressed (zipped) folder or Mail recipient appear as special entries handled by the shell)
How arguments are passed
When you “Send To” an executable or a script, Explorer launches that target with command‑line arguments — each selected file’s full path is supplied as a separate argument. That means properly authored scripts can process multiple files at once (send photos to an image‑resize batch, or send documents to an archiving script). Community technical writeups and shell guides demonstrate this behavior and show common script examples.
Why it still matters in Windows 11
Windows 11 redesigned the primary context menu and buried legacy options behind “Show more options” (or Shift+F10), which reduced visibility for Send To for many users. But the submenu itself is unchanged: the classic items still load and work as before when you access the legacy context menu. That means Windows 11 preserved the capability while modernizing the UI. If you prefer the old menu, there are ways to surface it more directly (temporary: Shift + right‑click / Shift + F10; permanent: registry tweaks to restore the classic menu), though those registry fixes come with maintenance caveats.
Practical takeaway: Send To remains an unglamorous but reliable productivity lever — a little folder that can meaningfully reduce repetitive file management steps without installing third‑party utilities.
Real‑world workflows: how people actually use it
Below are practical, repeatable ways to use Send To that scale from casual users to power workflows.
1) Fast organization — one‑click file routing
Add shortcuts to the SendTo folder for:
- Your common project folders
- A network share or NAS folder you use for archives
- “In‑box” folders for other people or processes
Now, instead of opening File Explorer, drilling to the destination, and dragging files, you can right‑click → Show more options → Send To → select the destination. It’s two or three clicks and no navigation friction. How‑to guides and user reports show this is one of the simplest productivity wins.
2) Open in a preferred app (Notepad++, image editor, converter)
Create a shortcut to your preferred application in SendTo. Right‑click a file and choose that app from Send To to open it instantly in your tool of choice. This is especially handy for tools that don’t appear in the “Open with” dialog or for workflows where you want to open many files in a non‑default app. Community tutorials and examples demonstrate adding Notepad or third‑party editors this way.
3) Batch processing with scripts
Place a batch file, PowerShell script, or a shortcut to a script inside SendTo. When you send multiple files to that script, Explorer runs it with each filename as arguments. Use cases:
- Resize images using ImageMagick or a wrapper script
- Batch‑convert documents
- Archive files into a dated folder
- Upload files to an SFTP server or trigger a client upload tool
Technical documentation and real‑world posts show examples where scripts accept %* or $args and handle file lists passed by Explorer. Remember to test scripts with spaces and long paths and consider quoting arguments in your script.
4) Cloud storage quick‑send
Add shortcuts to local synced folders for Dropbox, OneDrive, Google Drive, or a mounted cloud drive. Sending files to those shortcuts moves them into the sync client queue so they upload automatically. This simplifies manual backups — but it depends on the sync client being installed and online.
5) Device handoff (phone features)
Some modern Windows builds and companion apps expose “Send to phone” or Phone Link integration that appears similarly in File Explorer’s Send To area (feature‑gated and dependent on Phone Link and connected device state). This is a new, platform‑dependent evolution of the same workflow — check feature availability on your build and device. Community reporting indicates the feature appears for paired Android devices on supported builds.
Step‑by‑step: customize your Send To menu (practical guide)
- Press Windows + R to open Run.
- Type shell:sendto and press Enter. Explorer opens the SendTo folder (that’s the per‑user folder).
- To add a folder: right‑click → New → Shortcut, browse to the folder, name it, Finish. Or drag an existing desktop shortcut into the folder.
- To add a program: create a shortcut to the executable, or drag an existing shortcut into SendTo.
- To add a script: copy your .bat or .cmd into SendTo, or create a shortcut to it; scripts will receive full paths as arguments (%* / $args).
- To remove an item: delete the shortcut from the SendTo folder.
A few practical tips:
- If you want the program to open files with spaces robustly, create a small wrapper script that quotes arguments.
- For scripts that should not leave a visible console window, create a shortcut to cmd.exe /c or a small compiled wrapper and set the shortcut’s Run property to Minimized.
- Items you add affect only the current user; system administrators can deploy SendTo entries via user profiles or provisioning scripts if needed.
Advanced tips and examples
Creating a multi‑file image resizer
- Create a batch file, ResizeImages.bat:
- Example snippet (ImageMagick installed):
- magick mogrify -resize 1200x %*
- Place ResizeImages.bat (or a shortcut to it) in SendTo.
- Select several images → right‑click → Show more options → Send To → ResizeImages.
Explorer will pass each file path as an argument; ImageMagick will process each file. Community examples and script guides show this exact pattern. Test on copies first.
Using a shortcut to run a program with a specific switch
Some tools accept a “drop into” argument. If your tool needs a switch like -open, place a shortcut target like:
- "C:\Program Files\MyApp\app.exe" -open
Name the shortcut appropriately and put it in SendTo. Now “Send To → MyApp (open)” launches the app with that option.
Copy vs Move behavior
- Left‑clicking a Send To folder in the Send To menu copies files there by default.
- Holding Shift while selecting the Send To option typically moves the file instead. This behavior is longstanding in Explorer and can be used to switch between copy/move without writing special scripts. (Behaviour can vary with shell extensions and network locations.)
Troubleshooting & limitations
- “Send To” entries not visible: If an expected item in the SendTo folder doesn’t show, verify the folder path (shell:sendto) and ensure the target shortcut is valid and not blocked by security settings. Microsoft community threads routinely show cases where invalid shortcuts or missing hidden files cause oddness.
- Mail recipient missing or misbehaving: The Mail recipient entry is a special shell item that relies on MAPI/default mail client configuration. If Mail Recipient opens the wrong client, you may need to re‑set your default mail handler or repair the mail registration. Community posts show Thunderbird and Outlook interactions can be finicky.
- Zip action failures: The built‑in Compressed (zipped) folder sometimes fails silently on very long paths or network shares; when this happens, third‑party archivers (7‑Zip) provide more robust feedback. Users should be aware of path length and permission edge cases.
- Context menu visibility changes in Windows 11: Because Windows 11 places legacy items behind “Show more options”, you’ll either need to click that extra button or use Shift+F10 / Shift+right‑click to access Send To. Some registry tweaks restore the classic menu but can be reverted by updates and carry risk. Use caution when editing registry keys for UI behavior; lifewire and other guides cover the process and the associated warnings.
- Network and cloud dependability: Shortcuts to mapped or cloud paths only work if the network or sync client is online. For mission‑critical automation, prefer local staging folders or scripts that verify connectivity.
Security and governance considerations
- Executable risk: Any program or script you add to SendTo runs under your user context when invoked. Adding an executable you don’t trust creates a way for clicked files to launch untrusted code. Always verify scripts, and prefer signed binaries or wrappers you control. Enterprise environments should sandbox or vet SendTo additions.
- Per‑user scope: Because SendTo is per‑user, attackers with access to a user profile could add a malicious shortcut. Endpoint protection and standard profile hygiene help mitigate this. Administrators can enforce restrictions with policies and by controlling profile contents at provisioning time.
- Deployment fragility: Relying on SendTo for organizational workflows is brittle at scale unless you control user images or use a scripted provisioning process. Windows updates and shell behavior changes can modify how context menus surface; community archives note that third‑party editors or registry hacks to tweak menus are fragile across builds. For enterprise deployments, use managed config tools or PowerShell scripts during provisioning rather than UI tricks.
Why Microsoft left it alone (analysis)
The Send To mechanism is a sision point: Windows reads a directory of shortcuts and adds items to a menu. That design is low‑risk, easy to implement, and flexible, so there’s little incentive for Microsoft to remove it. In Windows 11, Microsoft focused on streamlining the primary context menu for broad usability while keeping legacy integrations intact — a compromise that preserved Send To but made it slightly less discoverable. Technical documentation shows the folder remains a known folder in current shell APIs, which is the most durable form of compatibility Microsoft provides.
Alternatives and complementary tools
- Quick Access / Pinned locations: For navigation, Quick Access and pinned folders in Explorer help reduce the need to send files.
- PowerToys and File Explorer add‑ins: Microsoft PowerToys (Image Resizer, PowerRename) add right‑click features for image resizing and renaming but don’t replace the simple routing flexibility of Send To. Use them in combination: PowerToys for file transformations, Send To for routing.
- Shell extensions (SendToSendTo, Send To Toys): Third‑party utilities can add GUI conveniences for editing Send To, but they add another maintenance dependency and potential security risk. If you prefer UI tools, choose well‑maintained, reputable projects and verify installers.
Historical context (short timeline)
- Windows 95 / 98 / XP: Send To established as a light shell extension mechanism to speed file transfers and application routing. Vintage forum discussions and early how‑tos reference it as a key right‑click utility.
- Windows 7 → Windows 10: The feature continued to be useful and well documented in tutorials and community posts.
- Windows 11: UI redesign buried the classic menu behind “Show more options,” but the SendTo folder and behavior were preserved in the KnownFolders API. Users need to access the legacy menu to see it unless they alter registry/UI behavior.
Verdict — when to use Send To and when not to
Use Send To when:
- You want a no‑friction, per‑user way to route files to recurring targets (project folders, cloud sync folders, simple scripts).
- You need a quick way to open files in a non‑default application without changing system associations.
- You prefer a low‑overhead customization that’s reversible by deleting a shortcut.
Avoid relying on Send To for:
- Critical, enterprise‑wide automation that must work identically across all devices without provisioning (it’s per‑user and can be fragile).
- Any workflow where security or code signing is mandatory — require signed binaries and vetted scripts.
- Situations where the UI surface must be discoverable for non‑technical users; unless you train them, Send To is hidden behind legacy menu access in Windows 11.
Final recommendations and a short checklist
- Try it: Press Windows + R, type shell:sendto, and add three shortcuts to folders or apps you use daily. Use it for a week and measure time saved.
- Script responsibly: If you add scripts, log their output to a known location and test on copies of data first.
- Secure your shortcuts: Prefer shortcuts to signed executables or to trusted scripts stored in a protected folder.
- Document for users: If you add SendTo entries for teammates, share simple instructions and include the exact path to shell:sendto.
- For IT admins: Deploy SendTo items during provisioning if you need consistency, and use signed scripts plus endpoint protection to mitigate risk.
Windows’ Send To is a classic example of a low‑visibility feature with outsized utility. It costs almost nothing to try, it’s reversible, and it integrates directly with the shell in a way modern add‑ons rarely match: no install, no extra permissions, and immediate effect. But it’s not magic — it’s a user‑level shortcut system that requires basic scripting hygiene and attention to security if you plan to automate. For power users who value quick, pragmatic gains in daily file handling, spending five minutes customizing shell:sendto yields a simple, enduring productivity payoff.
Source: MakeUseOf
This forgotten Windows XP feature still works in Windows 11 and it's incredibly useful