ADC - ArchivedDataCodec

ADC (ArchivedDataCodec) is an open-source file extension and archiving/compression tool that uses Zlib for efficient compression and decompression of various file types. With a simple command-line interface, ADC supports both Windows and Linux, making it easy for users to archive and extract files.

ADC Archiver uses an 8-byte header to identify and manage its archive format. This allows for efficient storage and retrieval of data, making it suitable for both personal and professional use.

Why ADC?

• ADC is open-source and driven by a community and me, Mealman1551 in my spare time.
• ADC is cross-platform, it works on Windows and Linux.
• ADC is easy to use, it has a simple command-line interface.
• ADC is efficient, it uses Zlib for compression and decompression.
• ADC supports a wide range of file types, making it versatile for various applications.
• ADC is designed for both developers and users, with a focus on usability and functionality.
• ADC is suitable for archiving and compressing files, making it a great choice for managing large datasets.
• ADC is actively developed and maintained, ensuring it stays up-to-date with the latest technologies and user needs.
• ADC is designed to be lightweight and fast, making it ideal for quick archiving and extraction tasks.

ADC for Every Archive

ADC Archiver can compress and archive any file, therefore it's really suitable for sorting and managing files and archives.

Cross-Platform

ADC Archiver is made for many platforms, may it be Windows or Linux, ADC is there for you.

Features

• Great Compression Algorithm: Utilizes zlib for efficient compression.
• Cross-Platform: Compatible with both Windows and Linux.
• Command-Line Interface: Simple and intuitive interface.
• Support: Supports a wide range of file types.

Getting Started

Prerequisites

Developers:

• python 3.12.x
• zlib library (typically included with Python)
• tkinter
• os
• colorama
• progress
• cryptography

Users:

• Windows 8 or higher
• A Linux distro with at least glibc 2.31 (glibc 2.31 support was introduced on 26-08-2025)

Downloads

Latest version: 1.4.3 LTS "Grand Canyon"

For Linux, you can download the tar.xz or tar.zst file and execute install.sh to install ADC Archiver. The install script will set up ADC and after installation, you can run ADC from the terminal using the command: adc ADC is compatible with Linux distributions that have glibc 2.31 or higher.

To remove run: remove.sh

Linux installation command

There is also a command to install ADC on Linux, this command requires xz-utils and wget

mkdir -p ~/adc-temp && cd ~/adc-temp && wget -O adc.tar.xz "https://gitlab.com/adc-project/tars/-/raw/main/adc.tar.xz?inline=false" && tar -xJf adc.tar.xz && sudo ./install.sh && cd ~ && rm -rf ~/adc-temp

To remove ADC on Linux, run this command:

wget -O- "https://gitlab.com/adc-project/bash/-/raw/main/remove.sh" | bash

You can browse other versions here

You can download test archives to test ADC. Click here to visit the test archive repository

ADC has multiple mirrors in case a specific server is unavailable:

• GitHub (original source)[Recommended]
• SourceForge Mirror

for more info about how to run on Linux see this: Documentation

Build ADC yourself

Sometimes you have problems with pre-compiled binaries, e.g. not supported architectures or a different operating system. In that case, you can build ADC Archiver yourself. You need to have Python3 installed, as well as the required libraries and a C compiler. After that, you can download the source code and build ADC with Makefile.

ADC has also a new program for OEM manufacturers and users called ADC Core Util

ADC Core Util is a program that only extract .adc archives, without needing the full ADC Archiver software. This is useful for OEM manufacturers and users who only need to extract .adc files without the additional features of the full ADC Archiver software. check it out.

ADC Canary: The Latest Live Development Version

ADC Canary is the active development branch of the project, focused on collaboration and rapid iteration. It receives the newest updates and is not intended for general use, but for developers who want to contribute. You can fork the Canary repository, make changes ranging from minor documentation edits to new features and submit a pull request. Once you've made 25 valid contributions, you will receive a Personal Access Token (PAT) that allows you to commit and push directly to the Canary branch (with limited permissions). Be sure to read the Code of Conduct in the main ADC repository to help maintain a positive and respectful environment.

Contributing

We welcome contributions to ADC! Whether you're a developer, designer, or just someone who wants to help:

You are required to have a GitLab account.

Steps to Contribute

1. Fork the Repository: Fork the repository to your own GitLab account.
2. Clone the Repository: Clone your forked repository to your local machine:

   git clone https://gitlab.com/Mealman1551/adc-canary.git

3. Modify the Code: Make your changes or fixes.
4. Commit Your Changes: Commit with a clear message:

   git commit -m "Your descriptive commit message"

5. Push Your Changes: Push to your fork:

   git push origin main

6. Create a Pull Request: Go to the original repository and create a pull request from your fork. Provide a clear description of your changes and why they are necessary.
7. Review and Feedback: Project maintainers will review your pull request. Be open to feedback and make changes if requested.

Note: Maintainers will review the diff and blame to see what you changed. Only change the lines you need. Changes are manually implemented to avoid merge conflicts due to frequent updates.

Code Style Guidelines

• Follow the existing code style and conventions.
• Use meaningful variable and function names.
• Write clear and concise commit messages.
• Document your code with comments where necessary.
• Run tests to ensure your changes do not break existing functionality.

Reporting Issues

If you encounter any bugs or issues, please report them on the issue tracker. Provide as much detail as possible, including steps to reproduce the issue, expected behavior, and any error messages.