.AC file extension

To open .AC files on Windows, confirm what you have: open a copy in a text editor—if it’s readable base64 with BEGIN/END-style lines it’s likely PEM; if it’s unreadable bytes it’s likely DER.

Open a .ac file with PKI/certificate tooling that supports X.509 Attribute Certificates, typically via inspection/validation features rather than a general-purpose viewer. The registered media type for this content is application/pkix-attr-cert (RFC 5877), and the file may be encoded as binary DER or text PEM.

Home Extension Index Certificates in index Certificates category page

Last updated: June 11, 2026 · Reviewed by Julian Stricker

What “reviewed” means on this page

Format fit: whether the “what is this file?” description matches common real-world use of the extension, including category, typical MIME types, and aliases.
Opening paths: whether Windows / macOS / Linux steps read plausibly for current OS dialogs and default apps; we remove fantasy menus and unsafe shortcuts.
Security framing: whether risk notes match the extension class (for example executables vs plain data) and whether affiliate wording does not contradict the security section.
Sources and further reading: whether external links point to vendors, standards bodies, or other primary references where possible; we avoid inventing details we cannot ground.
Limits: this is clarity and safety-messaging QA, not a guarantee that every statement is exhaustive or that every binary you download is harmless.

Full methodology in the Imprint — The Imprint also states where AI is used and what that does—and does not—replace.

Open on your device

Choose your operating system for a dedicated step-by-step opening guide.

How to open .AC files

Use these platform-specific instructions to open .AC files safely.

Windows

Confirm what you have: open a copy in a text editor—if it’s readable base64 with BEGIN/END-style lines it’s likely PEM; if it’s unreadable bytes it’s likely DER.
Use a PKI/certificate inspection tool that explicitly supports X.509 Attribute Certificates (ACs), then import/open the file for viewing/validation.
If your usual certificate GUI only handles public-key certificates (.cer/.crt), use a PKI toolchain that can parse ACs per RFC 5755 (many “certificate viewers” won’t).

Full Windows guide

Mac

Check encoding: view a copy in a text editor to distinguish PEM (text/base64) from DER (binary).
Open/inspect the file with PKI tooling that supports X.509 Attribute Certificates (application/pkix-attr-cert), not just standard identity certificates.
If macOS certificate apps won’t import it, validate/inspect it using dedicated PKI tools rather than Keychain-style certificate import workflows.

Full Mac guide

Linux

Use your desktop’s file properties or MIME database to see whether it identifies .ac as application/pkix-attr-cert (shared-mime-info may provide the mapping).
Inspect the contents with PKI tooling that supports attribute certificates (RFC 5755) and ensure you use the correct input encoding (DER vs PEM).
If the extension is misidentified, rely on the file’s content and the producing system’s documentation rather than the filename.

Full Linux guide

iOS

iOS typically won’t provide a useful preview for X.509 Attribute Certificates; transfer the .ac file to a desktop system and inspect it with PKI/certificate tooling that supports ACs.

Full iOS guide

Android

Android generally lacks built-in viewers for X.509 Attribute Certificates; if no specialist PKI app is available, move the file to a desktop OS for inspection/validation.

Full Android guide

Security notes

Treat .ac attribute certificates as sensitive authorization credentials: they may grant roles/privileges and should only be installed or provided to systems you trust.
Do not make trust decisions based on the .ac extension alone; confirm it is an X.509 Attribute Certificate and validate it according to your PKI/authorization policy (issuer trust and validity).
Even though an AC is “data,” it is typically processed by security parsers; avoid opening untrusted .ac files in obscure or unmaintained certificate tools.

If you did not expect this file

This extension is usually plain data, text, or structured content—not a program by itself. The practical risk is social engineering (a scam attachment or misleading filename). For trusted senders you rarely need heavy-handed antivirus wording; use these tools when you want an extra check on unexpected downloads.

Avast

Avast offers free and premium antivirus software that protects against viruses, malware, ransomware, and phishing. Scan files before opening them to ensure safety.

Norton

Norton 360 delivers comprehensive antivirus protection, VPN, and identity theft monitoring. Scan files for threats before opening to keep your device secure.

We may earn a commission when you use affiliate links. This supports our free file extension guides.

Can't open this file?

These are the most common causes and fixes when .AC files fail to open.

Common reasons

It won’t open in certificate viewers (only supports public-key certs)
DER vs PEM mismatch causes parse/import errors
Wrong assumption: the .ac file isn’t an attribute certificate
Validation rejected by an authorization system

Fix steps

Use PKI tooling that explicitly supports attribute certificates (RFC 5755 context), not only .cer/.crt workflows.
Confirm you are not trying to import it into a store expecting an identity certificate; treat it as an authorization object handled by your PKIX authorization system.

OS-specific troubleshooting

What is a .AC file?

A .ac file is most often an X.509 Attribute Certificate (AC): a signed X.509 structure that contains authorization attributes (e.g., roles or clearances) bound to a holder, separate from a public-key identity certificate. The Internet profile for attribute certificates is specified in RFC 5755. The media type application/pkix-attr-cert is registered for carrying a single X.509 attribute certificate and is commonly associated with the .ac extension (RFC 5877).

Background

Attribute Certificates are used in some PKIX-based authorization designs to separate identity (handled by a normal X.509 public-key certificate) from authorization (handled by an AC). This separation allows a system to change a user’s privileges without reissuing the user’s identity certificate, because the attributes live in a separate signed object.

In practice, .ac files show up in security/authorization deployments where software expects an “attribute certificate” object and verifies it according to the profile in RFC 5755 (issuer, validity period, holder binding, and attribute syntax). The IANA media type registry lists application/pkix-attr-cert and points to RFC 5877 as the authoritative specification for transporting a single AC.

Be aware that “.ac” is also used by unrelated formats (for example, AC3D model files and Autoconf-related files), so you should confirm the file’s origin and contents before assuming it is an attribute certificate.

Common MIME types: application/pkix-attr-cert

Common .AC issues

It won’t open in certificate viewers (only supports public-key certs)

Many GUI certificate apps focus on X.509 public-key certificates (identity certificates) and do not parse or display X.509 Attribute Certificates, even though both are “X.509”.

Use PKI tooling that explicitly supports attribute certificates (RFC 5755 context), not only .cer/.crt workflows.
Confirm you are not trying to import it into a store expecting an identity certificate; treat it as an authorization object handled by your PKIX authorization system.

DER vs PEM mismatch causes parse/import errors

The same AC content may be stored as binary DER or text PEM. Using the wrong mode (or expecting PEM when it is DER) often looks like “corrupt” or “unsupported format.”

Open a copy in a text editor: PEM is readable base64 with header/footer lines; DER is binary.
Re-run your inspection/import using the correct encoding option for the tool you’re using.

Wrong assumption: the .ac file isn’t an attribute certificate

The .ac extension is ambiguous and is also used for unrelated file types, so an “AC data” assumption can be wrong if the file came from a different workflow (e.g., modeling or build tooling).

Confirm the file’s provenance: did it come from a PKI/authorization system expecting an attribute certificate?
Check whether the system identifies it as application/pkix-attr-cert and whether the contents match an X.509 AC structure per RFC 5755.

Validation rejected by an authorization system

ACs are security credentials; consuming systems may reject them if the issuer is not trusted, the validity period is wrong, or the profile/attributes are not what the system expects.

Verify validity period and that the issuer matches what your environment trusts/accepts for attribute certificates.
Confirm the consumer expects an RFC 5755-profiled attribute certificate (not a different credential type) and that the attributes match the system’s policy.

FAQ

What is a .ac file most commonly?

Most commonly it is an X.509 Attribute Certificate (authorization certificate) used in PKIX systems, associated with the media type application/pkix-attr-cert (RFC 5877).

Is a .ac attribute certificate the same as a normal X.509 certificate (.cer/.crt)?

No. A public-key certificate binds an identity to a public key, while an X.509 Attribute Certificate carries authorization attributes and is profiled for Internet use in RFC 5755.

Why does my OS not know what to do with .ac?

Attribute certificates are typically consumed by specific PKI/authorization systems rather than end-user apps, and the .ac extension is also used by unrelated formats, so OS file associations are often missing or misleading.

Can I rename .ac to .cer/.crt to open it?

Renaming does not change the underlying type; tools that expect an identity certificate may still reject it because an attribute certificate is a different X.509 object.

Similar file extensions

Compare related formats in the same category to find the right tool faster.