# Find Gender in Excel and CSV Files with GenderAPI

> Upload a spreadsheet, review suggested columns, choose name, email or username analysis and export CSV results. Check supported formats, data handling and job limits.

Canonical HTML: https://www.genderapi.io/blog/determining-gender-of-names-in-excel-csv-with-gender-api

Last reviewed: 2026-09-27

## Run a file job from your dashboard

The GenderAPI file tool reads a spreadsheet, lets you map a name, email or username column and prepares enriched CSV output. Use it for a file-based job when you do not need to build an API integration.

The dashboard file workflow is separate from REST V2 batch requests. The file itself is not a V2 JSON request, and V2 per-item limits and response paths should not be applied to this native job.

- [Open the Excel and CSV tool](https://app.genderapi.io/csv)

## Use a format accepted by the upload control

The current upload control selects one file at a time. For a workbook with multiple worksheets, choose the intended sheet and review the parsed values. Export another format to a listed format before starting if the upload control does not accept it.

File complexity, row count, selected method, account credits and service load affect processing. Test a representative file; this guide does not promise a fixed maximum size or completion time.

| Format | Accepted extension |
| --- | --- |
| CSV | `.csv` |
| Excel | `.xls, .xlsx` |
| Apple Numbers | `.numbers` |
| OpenDocument | `.ods` |
| Tab-separated values | `.tsv` |
| Text | `.txt` |

## Review suggestions before starting the job

- Prepare a copy containing the data needed for the job. Keep the input type in a clearly labeled column and any reliable two-letter country codes in a separate column.
- Sign in, open the Excel and CSV tool, select the intended key and choose your file and worksheet.
- The tool can send sample cell data for AI-assisted column suggestions during worksheet setup. Check the suggested input type and columns yourself before continuing.
- Choose name, email or username analysis, confirm the source and optional country mapping, and review the current AI and export options shown by the tool.
- Start processing and monitor progress. Do not submit the same file repeatedly just because a job has not finished yet.
- When the export is ready, download the CSV, check row alignment and review resolved, unknown and failed records. Keep your source file for comparison.

## Check the file-job settings

| Setting | Type | Description |
| --- | --- | --- |
| API key | Account credential | The account whose balance the selected job will use. |
| File and worksheet | File selection | Choose one accepted file and the intended worksheet. |
| Method | Choice | Name, email or username. Review automatically suggested values. |
| Source column | Column mapping | The input to analyze in each row; check the header and sample values. |
| Country context | Optional column or setting | Use known two-letter country codes when relevant. |
| AI and export options | Current tool controls | Review the displayed settings before processing; these are not V2 ai_mode parameters. |

## Read the native result columns

The exported CSV adds native gender, country, probability and found_name result fields. Confirm the original row alignment and column headers before importing it into another system. The output format is CSV even when the input was an Excel workbook.

Predictions are inferred associations. Keep them separate from self-declared gender and verified country information.

- Inspect an ordinary result, an ambiguous input and a failed operation before processing a full dataset.
- A blank cell, the text null and a formula error are different spreadsheet values. Normalize unknown results deliberately without hiding errors.
- Use a neutral fallback for unknown or uncertain records. Keep supplied profile information separate from inferred columns.

| Output | Typical type | How to use it |
| --- | --- | --- |
| Gender | Text or unresolved value | Retain male or female only for a successful result. Preserve an unresolved value as unknown; review error text separately. |
| Probability | Number, when available | A legacy confidence signal. It is not the V2 confidence field or a measured accuracy rate for your dataset. |
| Country | Text, when available | Context returned by the lookup. Keep it separate from a customer's verified country. |
| Found or normalized name | Text, when available | The name used or extracted during processing. Review it for ambiguous emails and usernames. |

- [How to interpret confidence and limitations](https://www.genderapi.io/accuracy-methodology)

## Plan for credits, limits and repeated runs

A registered free GenderAPI account includes 200 credits per day. Credits are an account balance, not a promise of 200 successful results in every workflow. Check the selected key's balance and the tool's current processing options before starting.

Native add-ons and file jobs have their own processing paths. The REST V2 batch limit, AI options and per-request billing fields do not automatically apply to them. A repeated run or recalculation can submit fresh work; do not assume it is free.

Start with a small sample, retain completed results, and review the failed rows before rerunning. If you only need to repair a later export or destination update, reuse the results you already have.

- [Account plans and credits](https://www.genderapi.io/price)

## Account for setup analysis and file retention

Selecting a worksheet can send sample cells for AI-assisted column mapping before the final processing step. Do not assume that all data stays local until you press Start. Remove unnecessary columns and review the privacy policy before selecting a file containing personal data.

After exporting, use the available delete action when the workspace copy is no longer needed. The published policy describes scheduled active-system removal and backup retention; a deletion schedule is not evidence that every copy has already been removed.

- [File and query retention policy](https://www.genderapi.io/privacy-policy)

## When to use the direct V2 API

Use a separate HTTP integration when your application needs explicit AI options, per-item status, source, confidence kind and usage information from V2. Follow the V2 request and response contract; adding V2 field names to a native formula or existing add-on does not change that client's behavior.

- [V2 request parameters](https://www.genderapi.io/docs/v2/request-parameters)
- [V2 response fields](https://www.genderapi.io/docs/v2/responses)
- [Python V2 integration](https://www.genderapi.io/integrations/python)
- [Node.js V2 integration](https://www.genderapi.io/integrations/javascript)

## Does the uploader accept XLSM files?

The current upload control lists CSV, XLS, XLSX, Numbers, ODS, TSV and TXT. Export an XLSM workbook to a listed format and review the resulting values before uploading it.

## Are column suggestions always correct?

No. Review the suggested input type, header handling, source column and country mapping. Sample data may be sent for AI-assisted suggestions during setup.

## Will I receive the original Excel workbook back?

The documented file job exports CSV results. Check the exported columns and row alignment before importing them into your original workbook or another tool.

## Is this the same as a V2 batch request?

No. It is a dashboard file job with its own options and processing. Use the V2 batch documentation when you are constructing JSON requests in a custom integration.

## Reference sources

- [GenderAPI Excel and CSV workspace](https://app.genderapi.io/csv)
- [Direct V2 batch documentation](https://www.genderapi.io/docs/v2/batch)
- [GenderAPI account pricing](https://www.genderapi.io/price)
- [GenderAPI privacy policy](https://www.genderapi.io/privacy-policy)
- [Direct V2 request contract](https://www.genderapi.io/docs/v2/request-parameters)