Take potentially dangerous PDFs, office documents, or images and convert them to a safe PDF.
![]() |
![]() |
---|
Dangerzone works like this: You give it a document that you don't know if you can trust (for example, an email attachment). Inside of a sandbox, Dangerzone converts the document to a PDF (if it isn't already one), and then converts the PDF into raw pixel data: a huge list of RGB color values for each page. Then, in a separate sandbox, Dangerzone takes this pixel data and converts it back into a PDF.
Read more about Dangerzone in the official site.
You can also install Dangerzone for Mac using Homebrew: brew install --cask dangerzone
Note: you will also need to install Docker Desktop. This program needs to run alongside Dangerzone at all times, since it is what allows Dangerzone to create the secure environment.
Note: you will also need to install Docker Desktop. This program needs to run alongside Dangerzone at all times, since it is what allows Dangerzone to create the secure environment.
See installing Dangerzone for adding the Linux repositories to your system.
Dangerzone can convert these types of document into safe PDFs:
.pdf
).docx
, .doc
).xlsx
, .xls
).pptx
, .ppt
).odt
).ods
).odp
).odg
).hwp
, .hwpx
)
.epub
).jpg
, .jpeg
).gif
).png
).svg
).bmp
, .pnm
, .pbm
, .ppm
)Dangerzone was inspired by Qubes trusted PDF, but it works in non-Qubes operating systems. It uses containers as sandboxes instead of virtual machines (using Docker for macOS and Windows, and podman on Linux).
Set up a development environment by following these instructions.
Licensed under the AGPLv3: https://opensource.org/licenses/agpl-3.0
Copyright (c) 2022-2024 Freedom of the Press Foundation and Dangerzone contributors Copyright (c) 2020-2021 First Look Media
Yes, Dangerzone received its first security audit by Include Security in December 2023. The audit was generally favorable, as it didn't identify any high-risk findings, except for 3 low-risk and 7 informational findings.
Dangerzone gets updates to improve its features and to fix problems. So, updating may be the simplest path to resolving the issue which brought you here. Here is how to update:
0.4.1
invalid json returned from container
on MacOS Big Sur or newer (MacOS 11.x.x or higher)"Are you using the latest version of Dangerzone? See the FAQ for: "I'm experiencing an issue while using Dangerzone."
You may be attempting to convert a file in a directory to which Docker Desktop does not have access. Dangerzone for Mac requires Docker Desktop for conversion. Docker Desktop, in turn, requires permission from MacOS to access the directory in which your target file is located.
To grant this permission:
(Full Disk Access permission has a similar effect, but it's enough to give Docker access to only the directory containing the intended file(s) to be converted. Full Disk is unnecessary. As of 2023.04.28, granting one of these permissions continues to be required for successful conversion. Apologies for the extra steps. Dangerzone depends on Docker, and the fix for this issue needs to come from upstream. Read more on #371.)