Prepare PDF files for SharePoint upload

In most teams the SharePoint library grows faster than naming discipline does. Someone drags thirty PDFs from the download folder into the browser, and the library then shows Document (1).pdf, Scan_2024.pdf and final version_2.pdf side by side. Repairing that later takes real effort. The cheaper moment is before, in the local folder, while the files have not been synced or uploaded yet.

Download for free

Before & After

Document (1).pdf 2024-03-15_Abteilung-IT_Richtlinie_Passwort-Policy.pdf

Why before the upload and not after

Renaming a file inside SharePoint afterwards is possible but has side effects. The name sits inside paths that colleagues have long since passed around in mail, Teams messages and meeting notes. With synced libraries the change also has to reach every device, which causes conflicts and duplicate copies when files are open. And renaming thirty files one by one through the context menu costs an afternoon nobody planned for. In the local intake folder the same job is a batch run with preview and confirmation, and afterwards nobody uploads anything unnamed again.

Characters and lengths that upset SharePoint

SharePoint and OneDrive reject certain characters in file and folder names, among them quotation marks, colons, slashes, asterisks, question marks and angle brackets. Leading or trailing spaces and a trailing dot cause everyday trouble too. On top of that comes the limit on the total path built from library address, folders and filename, which deeply nested filing reaches quickly. A pattern that keeps date, department, document type and subject short and separates them with underscores or hyphens stays on the safe side. Where sender names carry accented characters, agree in advance whether to spell them out.

Set up once: one pattern per library

Libraries serve different purposes, so not all of them need the same pattern. A policy library does well with date, department, document type and title; a project library with a project code, date and document type. Define the pattern in Filery once and name the matching local intake folder accordingly, so that next time nobody has to work out which scheme applies right now. Keep the list of document types short and agree it in the team before you start. A pattern only one person knows lasts exactly as long as that person stays.

The route from intake folder into the library

In practice it runs like this: files land in the download or scan folder, Filery reads that folder, proposes names, you check the list and confirm. Then you upload, either by dragging into the browser, through the Files tab in Teams, or by moving the files into the synced folder. For the sync route one rule applies: rename first, move second. Reverse it and you trigger two sync operations back to back and risk colleagues having opened the older version already. For larger uploads it also pays to check the library afterwards to confirm everything arrived.

Columns beat filenames, and what happens to the content

In SharePoint, structured information belongs in library columns, not in the filename. A good name replaces neither metadata nor a retention policy; it helps in search results, in the file list, and in shared links that colleagues only skim. Filery addresses exactly that and does nothing else: it uploads nothing, moves no files and fills no columns. On content handling: the PDF is read on your computer and its content transmitted encrypted for AI analysis. The recognised metadata come back, the renaming then happens again in the file system, and the files are not stored permanently.

FAQ

You control the result through the naming pattern and see every suggestion before it runs. That lets you build a pattern using only safe characters, and you correct conspicuous individual cases directly in the list before confirming the pass and uploading.

No. Filery renames files in the file system. You upload as usual through the browser, through Teams or through the sync folder. That keeps the step independent of how your libraries happen to be configured and which permissions apply there.

Yes, as long as the files genuinely sit on the device and are not merely shown as placeholders. It is best to rename in the intake folder and move into the synced folder only afterwards, so two sync operations do not run back to back.

No, columns and metadata stay untouched. Filery changes the filename only. If your library derives values from the name, a consistent pattern helps with that; otherwise you keep maintaining the columns in SharePoint itself. A good naming pattern and well-kept columns complement each other; neither replaces the other.

Related topics

Prepare PDFs for DMS and ECM
Create GoBD-compliant PDF filenames automatically
Prepare PDF files for DATEV import

Download Now

Choose your platform and start with automatic document renaming

macOS

Universal (Apple Silicon & Intel)

Download (DMG)

Windows

Windows 10 & 11

Download (EXE)

We are currently working on official code signing for Windows. The download is already available – Windows Defender or SmartScreen may show a warning because the app is not yet certified. Choose “More info” → “Run anyway” to install.

System requirements: macOS 10.14+, Windows 10/11

All downloads are transmitted securely via HTTPS.