Cloud integration

How SharePoint files are processed in Filecraft

Open a file from any SharePoint document library, process it in your browser, and save it back — without the file ever touching Filecraft's infrastructure.

Your files stay within the Microsoft trust boundary — Filecraft never has custody.

Open a file from SharePoint How local processing works →

How it works

Follow your file from SharePoint to your browser and back. Filecraft never holds the bytes.

1
You browse your SharePoint sites
The cloud picker shows your SharePoint sites, document libraries, and files. Filecraft's server queries Microsoft Graph for metadata — it never downloads file content.
SharePoint → Your browser
2
You select a file
Filecraft's server requests a temporary download URL from Microsoft Graph. Your browser downloads the file directly from Microsoft's CDN — Filecraft's server is not in the path.
Your browser
3
Processing happens locally
The file is processed in your browser using Web Workers (for PDFs) or the Canvas API (for images) — the same local processing as any desktop file you drop.
Still your browser
4
You save back to SharePoint
Filecraft creates a pre-authenticated upload session with Microsoft. Your browser uploads the result directly to SharePoint — Filecraft's server handles only the session metadata.
Your browser → SharePoint

For regulated environments: Because files travel directly between your browser and Microsoft's infrastructure, Filecraft never has custody of your document content. This simplifies compliance conversations — your files stay within the Microsoft trust boundary throughout.

Open a file from SharePoint

Common questions

Which SharePoint sites can Filecraft access?

Filecraft lists the SharePoint sites available to your Microsoft account. You browse sites, then document libraries, then folders. It accesses only what you explicitly navigate to.

Does Filecraft download the entire document library?

No. Filecraft lists folder contents using Microsoft Graph metadata calls. Only the specific file you select is downloaded — directly to your browser, not to Filecraft's servers.

Can my IT admin see that I used Filecraft?

Your admin can see that you authorized a third-party app (Filecraft) through Microsoft OAuth. They can see metadata-level Graph API calls. They cannot see what Filecraft did with the file, because the processing happens locally in your browser.

What permissions does Filecraft need?

Filecraft requests Sites.Read.All to list SharePoint sites and document libraries, and Files.ReadWrite to download and upload files you select. It does not request admin-level or tenant-wide permissions.

How local processing works →How OneDrive files are processed →Pro plans with cloud integration →