File format · .s1h

Sealed HTML Document (.shtml) — SealedMedia Format Repair Guide

Sealed HTML documents are DRM-protected web pages created by SealedMedia. Learn how these files work, why they become inaccessible, and what recovery options exist.


Sealed HTML documents are protected web pages created by SealedMedia, an enterprise digital rights management (DRM) technology once used to control access to sensitive HTML content. These files allowed organizations to distribute web-style documents while enforcing permissions such as view-only access, expiration dates, and revocation — even after a file left the corporate network. At FileRepair.net, we help users understand these niche protected formats and what can be done when they become inaccessible or damaged.

What Is a Sealed HTML Document?

SealedMedia was a DRM vendor whose technology was acquired by Oracle and integrated into what became Oracle Information Rights Management (Oracle IRM). The platform could "seal" many common file types — HTML pages, Microsoft Office documents, PDFs, and images — wrapping them in an encrypted container that required authenticated client software to open. A sealed HTML document typically carried a distinct file extension and could only be rendered through the SealedMedia client (later the Oracle IRM Desktop client), which contacted a rights management server to verify the user's credentials and retrieve the decryption keys.

The sealing process encrypted the underlying HTML, embedded resources, and metadata, then bound the encrypted payload to a set of usage rights defined on the server. This meant that simply possessing the file was not enough to read it — the holder also needed a valid server-side policy granting access.

Key Technical Facts

Because SealedMedia was a proprietary, enterprise-grade DRM system, full public specifications for the sealed file container are limited. What can be stated with confidence is that these files function as encrypted wrappers around standard source content. The format relies on:

  • Symmetric encryption of the document payload, with keys managed centrally on the rights management server.
  • Policy-based access control, where each sealed file references a classification or policy category stored server-side.
  • Client-side decryption, performed by dedicated desktop software after the server delivers the necessary keys.

We do not invent or publish magic-byte signatures, MIME types, or internal structural details for this format. Where exact technical identifiers are needed, Oracle's official IRM documentation is the authoritative source.

Why Sealed HTML Files Become Inaccessible

Unlike most file-corruption scenarios, sealed documents typically become unreadable for reasons tied to the DRM infrastructure rather than file-level damage:

  • Server decommissioning. If the organization retired its SealedMedia or Oracle IRM server without a migration path, the files can no longer obtain decryption keys and are effectively locked.
  • Client software deprecation. The SealedMedia client and early Oracle IRM Desktop software are legacy products. Modern operating systems may not support them, leaving no way to open sealed files even when the server still exists.
  • Policy revocation or expiration. A file may be intact but its associated policy may have expired or been revoked, preventing access regardless of file condition.
  • Account changes. If the user's identity or group membership no longer matches the policy, the server will deny key delivery.
  • Genuine file corruption. Less commonly, the sealed container itself may be truncated, partially overwritten, or damaged in storage, preventing the client from parsing it even with valid credentials.

What Data Can Be Recovered?

Recovery depends entirely on the access scenario. If the rights management server is still operational and the user holds valid credentials, the file can be opened through the appropriate client and the underlying HTML content viewed or, if policy permits, unsealed back to a standard format.

If the server has been decommissioned or the client software is unavailable, recovery becomes far more difficult. The encrypted payload cannot be meaningfully extracted without the server-managed keys. In rare cases of partial file corruption where valid credentials and a working server exist, the intact portions of the HTML content may be recoverable.

We want to be straightforward with users facing orphaned sealed files: when the DRM infrastructure is gone, there is no reliable way to decrypt the content, and no reputable repair service can bypass the encryption without the original keys.

How Recovery Works

When a sealed HTML document is brought to us, our first step is always to determine whether the issue is infrastructure-related or file-related. We assess whether the original rights management server is reachable, whether the appropriate client can be installed, and whether the user's credentials are valid under the file's policy.

If the file is genuinely corrupted rather than simply locked, we examine the container structure to determine whether the encrypted payload is intact and whether the metadata needed for the client to request keys is readable. Where the damage is limited and the DRM infrastructure is functional, we work to reconstruct enough of the container for the client to open the document normally.

Frequently Asked Questions

Can I open a sealed HTML document without the SealedMedia or Oracle IRM client?

No. These files require the dedicated client software and a connection to the rights management server to decrypt and display content.

What if my company no longer has the IRM server?

Unfortunately, without the server the decryption keys cannot be delivered, and the file's content is not accessible. This is a fundamental limitation of the DRM design, not a repair issue.

Is there a tool to convert sealed HTML to regular HTML?

Unsealing is possible only through the official client when policy permits it. There is no legitimate standalone converter that bypasses the encryption.

Can file corruption in a sealed document be repaired?

If the container is damaged but the server and credentials are valid, partial recovery may be possible. If the encryption itself is intact but the server is gone, recovery is not possible.


If you have a sealed HTML document you cannot access, send it to FileRepair.net for a free evaluation. We will assess whether the problem is file-level corruption or an infrastructure limitation and give you an honest assessment of what — if anything — can be recovered.

Send us your .s1h file for a free evaluation

Our recovery engineers will tell you exactly what can be recovered — at no cost. There is no charge if we cannot recover your data.

Start a free evaluation