.CND file extension

To open .CND files on Windows, open the .cnd file in a text editor (for example Notepad) or an IDE to view/edit it as plain text.

To open a .cnd file, use a text editor or an IDE (it is plain text) and, if needed, import/register it with JCR software such as Apache Jackrabbit or other JCR implementations that support CND. If you received a .cnd from a content package workflow (for example, Jackrabbit FileVault), it is typically meant to be consumed by those tools rather than “viewed” like a word-processing document.

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 .CND files

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

Windows

  1. Open the .cnd file in a text editor (for example Notepad) or an IDE to view/edit it as plain text.
  2. If the file is meant to be applied to a repository, register/import it using your JCR tooling (for example, Apache Jackrabbit node type registration or a FileVault-based import workflow).
Full Windows guide

Mac

  1. Open the .cnd file with a text editor (for example TextEdit in plain-text mode) or an IDE to view/edit the definitions.
  2. To use it in a JCR repository, import/register it via your JCR tools (such as Jackrabbit or a FileVault-based content package workflow).
Full Mac guide

Linux

  1. Open the .cnd file in a text editor (for example Vim/Nano) or an IDE; it is plain text.
  2. If it is for deployment, register/import it with your JCR implementation’s tooling (commonly Jackrabbit-related workflows).
Full Linux guide

iOS

  1. You can usually view .cnd as plain text in a text editor app; if you need to register it into a repository, transfer it to a desktop/server environment where your JCR tools run.
Full iOS guide

Android

  1. Open the .cnd file in a text editor app to view it as plain text; for repository registration/import, move it to a desktop/server environment with JCR tooling.
Full Android guide

Security notes

  • .cnd is plain text and does not inherently contain macros or executable code, but importing it changes a repository’s content model; only register CND from trusted sources.
  • Be cautious when opening unknown .cnd files with complex tooling: parsing bugs in repository/import tools can be a risk; prefer well-maintained JCR tools and keep them updated.
  • Treat .cnd from content packages as configuration: a malicious or careless definition can introduce overly permissive structures or unexpected constraints that affect application behavior.

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.

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 .CND files fail to open.

Common reasons

  • The .CND file opens in the wrong app (or won’t open by double-click)
  • Repository import/registration fails due to syntax errors
  • Namespace or prefix conflicts during registration
  • CND changes do not take effect after deployment/import

Fix steps

  1. Open it explicitly with a text editor/IDE using “Open with…” and verify you can read it as text.
  2. Optionally change the default app association for .cnd to your preferred text editor.

What is a .CND file?

.cnd is the Compact Node Type Definition (CND) notation defined by the JCR 2.0 specification. It is a plain-text grammar used to declare JCR namespaces and node type definitions before they are registered in a repository. The official media type for this format is text/jcr-cnd.

Background

Other JCR-related software can also parse/import CND; for example, ModeShape provides an API for importing JCR Compact Node Definition (CND) files. Practically, most users open .cnd files in a text editor to inspect or edit the definitions, then use repository tooling (or build/deploy scripts) to register them.

Common MIME types: text/jcr-cnd

Further reading

Authoritative resources for more details on the .CND format.

Common .CND issues

The .CND file opens in the wrong app (or won’t open by double-click)

A .cnd file is plain text, but the file association on your system may be missing or pointing to an unrelated program.

  1. Open it explicitly with a text editor/IDE using “Open with…” and verify you can read it as text.
  2. Optionally change the default app association for .cnd to your preferred text editor.

Repository import/registration fails due to syntax errors

CND must follow the grammar defined by the JCR specification; minor typos, missing brackets, or invalid names can prevent parsing.

  1. Validate the file against the JCR 2.0 CND notation rules (Compact Node Type Definition grammar).
  2. Compare your definitions with working examples from your repository/tooling documentation (for example Jackrabbit’s node type notation documentation) and correct the syntax.

Namespace or prefix conflicts during registration

CND files can declare namespaces/prefixes; conflicts happen when the same prefix/URI is already registered differently in the target repository.

  1. Check the CND namespace declarations and ensure they match the target repository’s existing namespace registry.
  2. Adjust prefixes/URIs to align with your deployment conventions, then re-register.

CND changes do not take effect after deployment/import

In content package workflows, node type and namespace registration may only occur at specific import stages or be restricted by repository configuration.

  1. Confirm your tooling/workflow actually registers node types from the .cnd file during import (for example, the expected FileVault node types/namespaces handling).
  2. Re-run the import with the correct options/order and verify the repository reports the updated node type definitions.

FAQ

Is a .cnd file a “document” like Word or PDF?

Not typically. In most real-world uses, .cnd is a plain-text JCR Compact Node Type Definition file used by content repositories (for example Apache Jackrabbit) to define and register node types and namespaces.

What is the official MIME type for .cnd (JCR CND)?

The IANA-registered media type is "text/jcr-cnd".

Can I convert a .cnd file to JSON/XML by renaming the extension?

No. Renaming does not convert the syntax. If you need another representation, you would need tooling that parses CND and emits a different format (if your JCR tooling supports that workflow).

How do I tell if my .cnd is actually a JCR CND file?

Open it in a text editor and look for JCR CND-style namespace and node type definitions (as described in the JCR 2.0 CND grammar and Jackrabbit’s node type notation documentation). If it is not readable as text, it may not be a JCR CND file.

Similar file extensions

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