SDOC File Documentation
Summary
An .sdoc file is an Oracle IRM sealed Word document: an encrypted, rights-protected file, not an ordinary Word document. You cannot simply open it. It needs the Oracle IRM Desktop client connected to your organization's IRM server, plus a rights account that grants you permission. Without the server and your credentials, no software — Word included — can read it. To get an editable copy, an authorized user must remove the protection through IRM itself.
Technical details
| Feature | Value |
|---|---|
| Full name | Oracle IRM Sealed Word Document |
| File extension | .sdoc |
| MIME type | application/octet-stream |
| Format type | Encrypted / DRM-wrapped document (binary container) |
| Technology | Oracle Information Rights Management (IRM) |
| Developer | Oracle Corporation (formerly SealedMedia) |
| Introduced | SealedMedia; acquired by Oracle in 2006 |
| Sealed family | .sdoc (Word), .sxls (Excel), .sppt (PowerPoint) |
| Open standard | No — proprietary DRM |
| Encryption | Strong; keys held by the IRM server, not the file |
| Signature | None publicly documented |
| Requires to open | Oracle IRM Desktop + IRM server + granted rights |
| Rights enforced | Open, edit, print, expiry, watermark |
| Conversions | None by design (protection removed only via IRM) |
| Also uses .sdoc | SmartDraw and some note/editor apps (unrelated format) |
| Related extensions | .sxls, .sppt, .doc, .docx, .rpmsg |
| Specification | docs.oracle.com/cd/E29542_01/ |
What is an SDOC file?
An .sdoc file is an Oracle Information Rights Management (IRM) sealed document — a Microsoft Word document that has been encrypted and bound to a usage policy. Oracle IRM grew out of SealedMedia, which Oracle acquired in 2006. Its “sealed” file family includes .sdoc for Word, .sxls for Excel and .sppt for PowerPoint. Sealing wraps the original document in strong encryption and ties it to an IRM server, so the content stays protected wherever the file travels, and its rights — open, edit, print, expiry, watermark — are enforced every time it is opened.
Because of that, an .sdoc is a security container, not a document with readable content sitting inside. It is not a variant of DOCX that Word can simply parse; it is an encrypted envelope whose keys live on a server, not in the file. Everything about opening one follows from that design. Note that some unrelated programs (SmartDraw and certain note/editor apps) also save their own documents as .sdoc; those are a different file type that opens only in the program that created them. The dominant meaning, and the one described here, is the Oracle IRM sealed Word document.
How sealing works: encryption bound to a server
A sealed file is built from three logical parts, none of which lets you read the content on its own:
encryption envelope the original Word document, encrypted;
the keys are held by the IRM server, not the file
policy / classification a reference to the rights model that governs the file
(who may open, edit, print; expiry; watermark)
sealed payload the protected Office content, decrypted only at
open time by the IRM Desktop client
The encryption key is deliberately not stored in the file. Instead the sealed document references a classification held on the IRM server, and the actual decryption key is released only at the moment of opening, only to a client that can prove the user has rights. This is why copying the file, emailing it, or moving it to another machine changes nothing about its protection: the content is useless bytes until an authorized client contacts the server and is granted a key. The rights model can also expire access or force a watermark, and those rules are checked on every open rather than baked once into the file.
What you need to open one: three things at once
To open an .sdoc you need all three of the following present at the same time. Remove any one and the file is unreadable:
1. Oracle IRM Desktop the add-in that decrypts the file and hands it to Word
2. a network path to the IRM server that issued the seal
3. a rights account granting you rights to this document's classification
When all three are in place, IRM Desktop transparently decrypts the file and opens it in Word with only the actions your rights allow — you might be able to read but not print, or read but not copy text. Microsoft Word on its own cannot read a sealed .sdoc; it only ever displays the decrypted content through the IRM Desktop add-in after authorization. The common errors follow directly from the three requirements: “no rights” means your account has not been granted access to that classification (or the seal has expired), and “cannot contact server” means your device cannot reach the IRM server, typically because you are off the corporate network or VPN.
Why there is no sealed-to-Word converter
There is deliberately no tool that turns a sealed .sdoc into a plain .doc, .docx or PDF, because defeating that protection is the entire purpose of IRM. The only legitimate path to an unprotected copy is for an authorized user who holds “unseal” or “export” rights to remove the protection through Oracle IRM itself, which produces an ordinary document. Even printing to PDF is gated: it works only if your rights permit printing, and the output may carry a watermark. If you lack rights, the honest answer is to ask the document owner for an unsealed copy rather than to look for a converter.
This makes two categories of “solution” on the web untrustworthy. “Open .sdoc online” services cannot work, because a sealed file cannot be decrypted without the IRM server, so they are typically scams or data-harvesting. And any third-party “sdoc opener” downloaded from an unofficial site risks bundled malware. The file itself is an encrypted document, not executable, so it cannot run code, but installing an unofficial opener can. Obtain Oracle IRM Desktop only through your IT department, and handle the document under your organization's data-protection rules, since it is confidential by design.
Legacy status: orphaned .sdoc files
Oracle IRM is legacy enterprise software; the IRM Desktop downloads date to the early 2010s, and the product is uncommon outside organizations that deployed it. Most people who meet an .sdoc received it from an employer or a business partner and simply need to be granted rights or to ask for an unsealed copy. A harder case arises when an organization migrates off Oracle IRM: old sealed files can be left orphaned, still encrypted but with no live server to authorize them. Recovering those requires access to the original IRM infrastructure and keys, which is an administrative and archival problem rather than something an end user can solve with a file tool.
Frequently asked questions
How do I open an SDOC file?
If it is an Oracle IRM sealed Word document, install Oracle IRM Desktop and sign in to your organization's IRM server; with the right permissions it opens in Word. Without the server and an authorized account it cannot be opened. If the .sdoc came from a drawing or note app instead, open it in that program.
Why can't Microsoft Word open my SDOC file?
A sealed .sdoc is encrypted and bound to an IRM server. Word can only display it through the Oracle IRM Desktop add-in after you have been granted rights. On its own, Word sees an unreadable protected container.
How do I remove the protection or convert SDOC to a normal Word file?
Only someone with “unseal” or “export” rights can remove the protection through Oracle IRM — there is no third-party converter, by design. Ask the document owner for an unsealed copy if you need to edit or print it.
References
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.