> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/introduction/product-comparison.md).

# Product Comparison

Compare Coresignal products by record coverage, file formats, processing levels, and delivery options.

Not sure which product to choose? Compare the differences:

1. [Record count](#id-1.-record-count). We offer millions of records going back to 2016.
2. [File formats and size](#id-2.-file-formats-and-size). We offer data in JSONL, Parquet, and CSV formats.
3. [Delivery formats](#id-4.-delivery-formats). We provide data as datasets (flat files) or data API.

### 1. Record count

Coresignal's products have various processing levels.

| Data source       | Record count | Scraping since |
| ----------------- | ------------ | -------------- |
| Company Data      | 72M+         | July 2016      |
| Employee Data     | 915M+        | July 2016      |
| Jobs Data         | 486M+        | August 2020    |
| Social Posts Data | 1.2B+        | February 2025  |

### 2. File formats and size

Coresignal provides data in **JSONL, Parquet, and CSV formats**. Each format results in a different file size.

{% hint style="info" %}
**JSONL/Parquet or CSV?**

* **Data in JSONL/Parquet format is sorted by country**. In the JSONL/Parquet format delivery, data is organized by country, with each country having its own folder. Inside each folder, you'll find multiple `.json.gz` or `.gz.parquet` files. A single JSONL file can contain up to 100,000 records.
* **Data in CSV format delivery is sorted by entity type**. In the CSV format delivery, data is organized by entity type, following a schema-based structure. Each folder represents a different entity, and related information is stored separately, requiring joins to establish connections between datasets. A single CSV file can contain up to 10 million records.
  {% endhint %}

***

### 4. Delivery formats

Coresignal delivers data as datasets (flat files) or data APIs. Each method has its benefits – please check the information below.

{% hint style="info" %}
**Dataset or data API?**

* **Datasets**. Best choice if you need a large dataset for a large-scale project or seek to use years of historical data. You can choose to get regular daily, weekly, or monthly updates, or one-time delivery.
* **Data APIs**. You can set up a data API and access fresh records on demand. Good choice if you want to integrate data into your product, easily enrich data, and need more flexibility in accessing records.
  {% endhint %}

**Incremental or full delivery?**

Incremental delivery includes records that were updated in particular month, while full delivery will include all available records.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/introduction/product-comparison.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.