> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/guides/create-and-manage-datasets/upload-tabular-data-as-tables.md).

# Upload tabular data as tables

Redivis offers extensive tools for previewing tabular data and transforming it in workflows, but the data needs to be uploaded correctly in a tabular format for researchers to utilize these tools.

This guide assumes you have already started by [Creating a dataset](/guides/create-and-manage-datasets/create-and-populate-a-dataset.md).

## 1. Locate the data you want to upload

You can [upload data](/reference/datasets/create-and-edit-datasets/import-tabular-data.md) directly from your computer, or import from a linked account.

If importing, you'll want to get the relevant external account configured to your Redivis account before getting started.

The import tools allow for multiple uploads, so no need to combine files together before importing them, but it's helpful to have them all in the same place.

## 2. Create tables

The first step to uploading data is to create one or more tables that the data will be uploaded to on your dataset.

Your data files may or may not be how you want to store them on this dataset, so it's important to think about your data's structure before getting started.

If you have multiple files that all follow the same schema, uploading them as one table improves their usability. For example, if each table represents a state, researchers could query across all states without having to join 50 tables first. Tables shouldn't be split for performance reasons. Even when querying billions of records, Redivis will execute in seconds.

When uploading files to tables, every row in a table should represent the same [entity](/reference/glossary.md#entity). You wouldn't want to combine county-level and state-level observations in one table.

If you haven't already, experimenting with the reshaping and analytic tools in a workflow might inform how you structure the dataset during this setup process and can save time for everyone. You can add your unreleased dataset to a workflow for testing by selecting **View dataset page** from the dataset overview, and then [add the unreleased dataset to your workflow](https://docs.redivis.com/guides/create-and-manage-datasets/pages/bo1ysFcttJEhasfakhYF#1.-create-a-project).

When you're ready select **Create new table** on the **Tables** tab of the dataset page and name your table to get started.

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FyV4vcToxQN3GKY34SFnH%2Fredivis-staging.com_Demo_admin_datasets%20(4).png?alt=media&amp;token=15658242-5ee4-4853-bdee-cb4ca1aacd37" alt=""></div>

## 3. Upload tabular file(s) to create a table

Start by selecting a data source. By default this is your computer, but you can choose any option from the dropdown menu.

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2F5Orm6WFQdX6FAc7UVlxM%2Fredivis-staging.com_workspace_datasets%20(6).png?alt=media&amp;token=51c91803-dd75-4afa-a3da-cf138451ef3d" alt=""></div>

Next, choose the file or enter the paths of the file you want to import.

If you select multiple files, they are automatically appended in this table based on common variable names. If a variable is missing in some files, it will be recorded as `null` for all records in that file.

For a full list of supported file types, as well as advanced functionality, such as wildcard imports, and error handling techniques, consult the [Uploading data reference](/reference/datasets/create-and-edit-datasets/import-tabular-data.md#overview).

Once you have chosen your files, select **Import**. If the files are coming from your computer, you may need to wait until they are finished uploading to the browser before they can be imported into Redivis.

*Learn more in the* [*Uploading data*](/reference/datasets/create-and-edit-datasets/import-tabular-data.md) *reference section.*

## 4. Verify uploads

As you upload files, you will see an overview of their progress and can view each file's data and additional information by selecting it.

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2F1kqOykTxrxr2RMJ1CZa3%2Fredivis-staging.com_workspace_datasets%20(8).png?alt=media&amp;token=c461da26-544b-4b88-a17e-8705adf1eb2c" alt=""></div>

Once all uploads are complete, you can inspect the table. Make sure to check the summary statistics and other analytical information to validate that the data is as you expected.

If you have more files to upload, you can **Manage imports** on the table at any time, up until releasing this version of the dataset.

## Next steps

#### Continue uploading your dataset

Great metadata makes your dataset usable. Complete your metadata, along with configuring access, creating a sample, and releasing this version.

*Learn more in the* [*Create & manage datasets*](/guides/create-and-manage-datasets/create-and-populate-a-dataset.md) *guide.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.redivis.com/guides/create-and-manage-datasets/upload-tabular-data-as-tables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
