The documents you upload are encrypted in-flight and at rest.

Data transmission between your browser and our site is encrypted and authenticated using TLS 1.2, ECDHE_ECDSA with X25519, and AES_128_GCM.

Our disk storage security is: AES-256 encryption (256-bit keys); XTS for block cipher mode; SHA-256 for key derivation; and PBKDF2 for key stretching.

You control access to your content using slideXchange’s Share functionality.

From a physical disk perspective, your uploaded files sit on a server behind a firewall. The server is not directly accessible from the Internet. The slideXchange team that accesses this server to deploy software upgrades, does not have the encryption key to the content and therefore cannot access user content.

SlideXchange is hosted at UpCloud’s datacenter in London. The data backups are also located in London.

When you send your deck as an email attachment, you can no longer update it without having to send another email. You’ve lost control of your IP and who has access to it. You don’t know how your deck will look on the recipient’s computer or mobile. Maybe the fonts you’ve used aren’t available. Or if you’re produced your deck on an Apple computer, and it’s viewed on a Windows device, layout changes can occur. Finally, you don’t know if your deck was opened and what slides were looked at.

With slideXchange all these issue are addressed. Plus, if your recipient opens your deck on their phone, it’s frictionless to click on a link and open it in their default browser versus downloading a file and opening it with a specific app.

Yes, you can share using most shared drive platforms. There is a subtle yet important difference. Shared drives are best used when collaborating with co-authors or reviewers. It is generally the workspace for generated documents.

Our view is that once a deck is ready to be shared, simply drag it on to slideXchange and then share it from there. This creates a healthy separation between your work area (shared drive) and your deployment space (slideXchange). And to further support this approach, in slideXchange you don’t manage access rights and permissions… you manage Shares. Which makes it really easy to see your sharing history.

SlideXchange is FREE. DocSend and sales enablement tools are expenseive.

DocSend and sales enablement tools have more functionality. The initial set-up in order to become productive is longer. In some instances such platforms can be complicated when all you’re trying to do is share a deck.

SlideXchange is just focused on sharing your deck. It is simple to use, doesn’t require change management effort within teams, and adoption is immediate. There is no ramp up time required.

No, you do not need to re-share the link to the uploaded document. You can update a file as many times as you like without any change to the shared link.

This means that post-sharing, you can update your content without disturbing your recipients. They won’t know that an update has been made unless you choose to notify them.

One best practice is to use the usage metrics in slideXchange to see what slides have been looked at and by whom, so you can notify only the relevant users if material changes have been made.

SlideXchange does not integrate with Google Drive and Google Slides. And it does not recognize the Apple Keynote file format.

However, you can export to PDF from both Google Slides and Apple Keynote, and upload the PDF file to slideXchange.

PowerPoint occasionally renders differently based on the hardware and operating system that it’s running on. This results in slight differences in how icons or image borders appear. And if a non-standard font used in the deck is not available in slideXchange, it results in a substitute font being selected.

So, if you upload a PowerPoint deck to slideXchange and notice that it looks slightly different from your computer… then to fix the issue… in PowerPoint, export your deck to PDF and upload that file to slideXchange. With PDF files there are no rendering issues.