> For the complete documentation index, see [llms.txt](https://ailyze.gitbook.io/ailyze-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ailyze.gitbook.io/ailyze-docs/troubleshooting/upload-issues.md).

# Upload Issues

This page helps you fix problems that come up when you add files to a project.

## "My file type isn't accepted / the file is greyed out"

Each workflow only accepts certain file types, so a file for the wrong workflow shows as greyed out.

| Workflow         | Accepts                                                      |
| ---------------- | ------------------------------------------------------------ |
| Analyze docx/pdf | `docx`, `pdf`, `txt`                                         |
| Analyze xlsx/csv | `xlsx`, `csv`                                                |
| Translate files  | `docx`, `pdf`, `xlsx`, `pptx`, `html`, `txt`, `xliff`, `srt` |
| Transcribe       | 30+ audio/video formats                                      |

1. Convert the file to an accepted type (for example, save a Google Doc as DOCX).
2. Or switch to the workflow that accepts your file.
3. Note that CSV is **not** accepted for translation — you can only analyze it later.

For the full list, see [Supported file types](/ailyze-docs/reference/supported-file-types.md).

## "I hit a file or size limit"

Every workflow has a cap on how much you can add to one project.

* Documents: up to **50 files** per project.
* Spreadsheets: **1 file**, about **5,000 rows** per project.
* Translation: up to **10 files**, up to **1,000,000 characters** each.
* Transcription: up to **5 GB** per file.

1. Split your data across more than one project.
2. Or trim an oversized file before uploading.

For all caps in one place, see [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).

## "Where did my uploaded file go?"

Nothing is lost — every file you upload is saved to your file library so you can reuse it.

1. Look in the folder tree on the create screen, or open **Manage Files**.
2. Select the file you want instead of uploading it again.

For more, see [Upload & manage files](/ailyze-docs/getting-started/upload-and-manage-files.md).

## "Cloud import isn't working"

Cloud imports need an active connection and a pop-up window, so a blocked pop-up or an expired login can stop them.

1. Re-authorize the connection when prompted, and allow pop-ups for the site.
2. For **Zoom**, remember that only your accessible **cloud recordings** appear.
3. If it still fails, use the **Local Files** tab to upload from your computer instead.

## "The configuration options didn't appear"

The setup steps only show after you have selected at least one file.

1. Add a file to the project first.
2. The options appear below once a file is selected.

## "My PDF didn't analyze well"

Scanned or image-only PDFs have no selectable text, so there is nothing for the analysis to read.

1. Use a text-based PDF instead of a scan.
2. Or transcribe the PDF into text first.
3. For interviews, upload **DOCX** for the best results.

## Still stuck?

* Try a different browser, or turn off aggressive ad-blockers, then upload again.
* Re-attempt with a smaller file to tell a size problem apart from a file-type problem.
* Contact support if it still won't work — Pro plans get faster responses. See [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).


---

# 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://ailyze.gitbook.io/ailyze-docs/troubleshooting/upload-issues.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.