File format · .s1g

Sealed GIF (.sgif) Files — SealedMedia Format & Recovery

Sealed GIF (.sgif) files are rights-protected images wrapped by SealedMedia's DRM technology. Learn how these sealed files work, why they become inaccessib


Sealed GIF (.sgif) files are rights-protected image documents created by SealedMedia, an enterprise digital rights management (DRM) technology that was acquired by Oracle in 2008. The "sealing" process wrapped a standard GIF image inside an encrypted container, allowing organizations to control who could view, print, forward, or modify the image long after it left their network. While SealedMedia was once widely deployed in financial services, government, and defense for secure document distribution, the technology has been largely discontinued, leaving many organizations with .sgif files they can no longer open.

What Sealed GIF Files Are and Who Used Them

SealedMedia produced a family of "sealed" file formats — .sdoc for Word documents, .sxls for Excel spreadsheets, .sppt for PowerPoint, .spdf for PDFs, and .sgif for GIF images. Each sealed file contained the original content encrypted and bound to a set of usage policies. To open a sealed file, a user needed the SealedMedia client (Unsealer) installed, an active network connection to a SealedMedia policy server, and valid authorization credentials.

The GIF variant was used when organizations needed to distribute diagrams, charts, scanned forms, or branded imagery with strict access controls. A sealed GIF might carry policies permitting viewing only on specific workstations, blocking screenshots, expiring access after a set date, or requiring online re-authentication each time the file was opened. The format saw peak adoption in the mid-2000s among enterprises that needed persistent document protection beyond what standard file permissions or simple password protection could offer.

Structure and Technical Characteristics

A sealed GIF file is not a standard GIF with an appended wrapper. It is a distinct encrypted container. The original GIF image data — including its header, logical screen descriptor, global color table, image data blocks, and any animation frames — is encrypted and stored inside the SealedMedia container along with metadata describing the content type, the policy server that governs access, and the rights template applied.

We do not document a specific file signature or MIME type for .sgif files because authoritative SealedMedia technical specifications are no longer publicly distributed. Oracle's acquisition documentation and legacy enterprise knowledge bases are the most reliable remaining references for the internal container structure. What can be stated with confidence is that the encryption is applied at the container level: the GIF's internal structure is not directly parseable by standard image libraries until the container is successfully unsealed and decrypted.

Why Sealed GIF Files Become Inaccessible

The most common reason .sgif files become unreadable today is infrastructure loss. SealedMedia's licensing and policy server model depended on the originating organization maintaining an active SealedMedia server environment. When Oracle integrated and eventually sunset the product line, many policy servers were decommissioned. Without a reachable policy server to authenticate against, the Unsealer client cannot retrieve the decryption keys, and the sealed GIF remains locked.

Additional failure scenarios include:

  • Client software loss: The SealedMedia Unsealer is no longer widely available for download, and current operating systems may not support the legacy client versions that remain.
  • Expired or revoked policies: Files sealed with time-based expiration policies may have permanently lapsed, even if a policy server could theoretically be reached.
  • Credential loss: Access was often tied to LDAP or Active Directory identities. When user accounts are deactivated or organizational directories are restructured, the binding between a user and their sealed-file rights can be broken.
  • Container corruption: As with any binary file, .sgif files can suffer bit-level corruption from storage failures, incomplete transfers, or improper backups, damaging the container header or encrypted payload.

What Data Can Potentially Be Recovered

Recovery prospects for sealed GIF files depend heavily on the specific circumstances of access loss:

  • With a functioning SealedMedia environment: If the original policy server (or a restored instance) is available and credentials are valid, the file can be unsealed normally, recovering the complete original GIF with full image quality and animation intact.
  • With the Unsealer client but no server: The client may cache decryption keys locally for offline use. In some configurations, previously opened sealed files remain accessible from a local credential cache, allowing recovery of the embedded GIF.
  • With container corruption but valid keys: If the encryption envelope is intact but the container has structural damage, it may be possible to repair the container wrapper and then proceed with normal unsealing.
  • Without keys or server: If the policy server is permanently gone and no local key cache exists, the encrypted GIF payload cannot be decrypted through conventional means. The encryption used by SealedMedia was designed to be robust, and there is no legitimate bypass for the DRM layer.

How Recovery Works

Recovery of sealed GIF files is fundamentally different from repairing a standard corrupt GIF. The challenge is almost always the DRM layer rather than the image data itself.

For organizations that still possess their SealedMedia server infrastructure, recovery is a matter of restoring the policy server, ensuring user accounts and rights templates are intact, installing a compatible Unsealer client, and then opening the .sgif file normally. Once unsealed, the recovered GIF can be saved in its standard, unencrypted form.

When the original SealedMedia environment is no longer available, recovery requires a forensic approach. Our team examines the container structure to determine the SealedMedia version, identifies the associated policy server from container metadata, and assesses whether any local key material or cached credentials survive on the workstations that originally opened the file. In cases of container corruption, we can often repair the wrapper structure to restore the file to an unsealable state.

It is important to be transparent: if the encryption layer is intact and no key material or authorized server environment exists, the embedded GIF image data is not recoverable through file-repair techniques. File repair addresses structural and format-level damage — it cannot break encryption or circumvent digital rights management. In those situations, the path forward is typically through the organization's IT or records management team to locate archived policy-server backups or alternative copies of the content in unsealed form.

Frequently Asked Questions

Can I convert a sealed GIF to a regular GIF without the SealedMedia software?

No. Converting a .sgif to a standard .gif requires unsealing the file through the SealedMedia Unsealer client with valid authorization from the governing policy server. There is no standalone converter that bypasses the DRM layer.

Is the SealedMedia Unsealer still available for download?

Official distribution of the SealedMedia Unsealer has been largely discontinued following Oracle's acquisition and integration of the technology. Some organizations may retain internal copies in software repositories or deployment images.

Can file-repair tools remove the DRM encryption from a sealed GIF?

No. File-repair tools address structural corruption within file formats. They cannot and do not circumvent encryption or digital rights management. If the encryption is intact, the original GIF can only be recovered through authorized unsealing.

Are sealed GIF files the same as password-protected GIFs?

No. Password-protected GIFs are not part of the standard GIF format specification. Sealed GIF files use enterprise-grade DRM with server-based policy enforcement, which is fundamentally different from simple password protection.

What should I do if my organization has hundreds of inaccessible .sgif files?

The first step is to determine whether any SealedMedia server backups or Unsealer installations survive in your environment. If the original content exists in unsealed form elsewhere — for example, in document management systems, shared drives, or email attachments — recovering those copies is often more practical than attempting to restore the full SealedMedia infrastructure.


If your organization is working with inaccessible or damaged Sealed GIF files, we can help evaluate the situation. Our team will assess your .sgif files, examine the container structure, and provide an honest assessment of what recovery is possible given your specific environment. Contact us for a free evaluation — we will let you know upfront whether your sealed files can be recovered or whether alternative approaches are needed.

Send us your .s1g 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