Skip to content

Convert DIC to TXT

Convert dictionary or DICOM .dic files to readable TXT with the correct local tool.

Make TXT files online

We can't read DIC files yet, so this conversion isn't available. If you can export your work to one of these formats - or others - we'll turn it into TXT:

Want to convert DIC to TXT?

Let us know. We pick the conversions to add next by how many people ask for them.

How to convert dic to txt file

A dictionary editor, search tool, or import utility may require entries as a plain .txt file instead of a .dic file. The correct conversion depends on whether the file is a word-list dictionary, a proprietary dictionary database, or a DICOM medical file using the less common .dic extension.

What the DIC format is

.dic is an ambiguous filename extension, not one universal format. The most common type is a spelling dictionary used by Hunspell, LibreOffice, OpenOffice, and compatible language tools. A Hunspell dictionary normally starts with a word-count line and then contains entries that may include affix flags; a matching .aff file defines how those flags generate word forms.

Other programs use .dic for simple word lists, custom glossaries, or proprietary dictionary databases. A less common use is DICOM medical data, which normally uses .dcm but can also have a .dic extension. DICOM is binary medical data, not a text dictionary; its file meta-information may contain the DICM marker at byte 128, but that marker is not present in every valid DICOM file.

What the TXT format is

.txt is a plain-text format readable by Notepad, Notepad++, Visual Studio Code, LibreOffice, shell utilities, scripts, and database-import tools. It stores characters and line breaks without requiring dictionary-specific software.

TXT is suitable for inspecting entries, searching and replacing text, comparing word lists, and transferring readable data between systems. It does not retain Hunspell affix rules, validation behavior, typed DICOM elements, image pixels, or proprietary application structure unless those details are deliberately exported as text.

Convert a dictionary or word list

  1. Copy the original .dic file and its matching .aff file, if one exists.
  2. Open the copy in Notepad++, Visual Studio Code, or another editor that lets you choose the character encoding. A first line containing a number and entries with slash-separated flags suggest Hunspell syntax; one entry per line usually indicates a simple word list.
  3. Use File → Save As, name the output dictionary.txt, and preserve the source encoding when another program depends on it. Choose UTF-8 when the receiving program supports it, especially for multilingual data.
  4. Inspect the saved file for a Hunspell count line, affix flags, unusual line endings, and incorrectly displayed accented characters. Remove dictionary syntax only if the destination expects one ordinary word per line.

If the file is already plain text, copying it with a new extension is enough; this changes no content:

cp dictionary.dic dictionary.txt

To convert a known source encoding to UTF-8 on macOS or Linux, use:

iconv -f WINDOWS-1252 -t UTF-8 dictionary.dic > dictionary.txt

Replace WINDOWS-1252 with the actual encoding. Do not guess: an incorrect source encoding can permanently damage accented or non-Latin characters.

For structured dictionary formats, use PyGlossary rather than a text editor. Install it from its official project source, open the input format, select a plain-text output format, configure encoding and field separators, and export. PyGlossary supports many dictionary formats but not every proprietary .dic variant; confirm that it identifies the file before exporting.

Online conversion is appropriate only for a non-sensitive dictionary whose exact format is explicitly supported by the service. Many general services reject .dic files or treat structured dictionaries as arbitrary binary data, so verify the output and do not upload files containing licensed, private, or proprietary content. Local PyGlossary, Notepad++, and VS Code avoid that exposure.

Convert a DICOM file with a .dic extension

First identify the file with a DICOM-aware application. Do not open it in a word processor or rename it and assume it is a dictionary. With DCMTK installed, run:

dcmdump input.dic > metadata.txt

This writes readable DICOM elements and values to metadata.txt. It does not convert image pixels into text and may expose patient identifiers. DICOM applications such as 3D Slicer, Horos, or RadiAnt can export selected metadata or reports when a structured or graphical result is required; available commands vary by application and version.

Quality and compatibility limits

Changing .dic to .txt does not translate, clean, or normalize dictionary data. A Hunspell export may still contain a count header and flags rather than a clean list of words, and removing those fields can make the original dictionary unusable. Keep the original files unchanged.

Check encoding, line endings, duplicate entries, capitalization, and whether the destination expects one entry per line or a delimiter-separated format. Never upload a possible DICOM file to an online converter because it may contain protected health information; use local DICOM software and follow applicable privacy rules.

Information about file extensions and file types is provided by File-Extensions.org

Frequently asked questions

Will a .dic file become readable when converted to .txt?

It depends on what the .dic file contains. A dictionary file may already be text, while a DICOM file is a medical-image format that needs a suitable tool to export readable information.

Will converting a DICOM .dic file to .txt preserve the image?

No, a text export does not preserve the medical image as an image. It can contain readable metadata, but the pixel data needs an image format to remain viewable.

Will a dictionary .dic file keep its rules when converted to .txt?

The word entries may remain readable, but dictionary rules are often stored separately in an .aff file. A plain text copy does not combine those rules with the entries.

Why does my .dic file look garbled as text?

It may be a DICOM file with binary image data, or the text may use an encoding that your text viewer does not recognize. Identifying which kind of .dic file it is determines the appropriate conversion.

Already downloaded

This file has already been downloaded. For your privacy it was deleted from our server right after the download, so it cannot be downloaded again. To get it once more, convert the file again.