Export LinkedIn Recruiter candidates to CSV or Excel

Use the table to choose a starting point. If the recipient needs a working Excel file, both CSV and XLSX can be opened in Excel. That does not make their contents interchangeable.

For the native CSV route, LinkedIn's instructions start inside a project. If you are still on a search-results page, the documented export there is PDF.

Open the project's Applicants tab. LinkedIn documents exporting a selected subset or using Export all to XLSX. It also offers applicant PDFs in a ZIP file. Choose XLSX when the next task is reviewing rows, filtering candidates or preparing a spreadsheet handoff.

The applicant workbook can include a LinkedIn profile URL, names, current role and company, contact details, application date, stage, screening questions and responses, and job or project identifiers. Hiring Assistant evaluation fields are included when that feature is enabled.

Apply Starters have a specific gap: LinkedIn says their email, phone and ZIP fields are blank because of data-sharing limits. Changing the file format will not recover those fields.

Start with your plan. LinkedIn's profile-export Help explicitly says Recruiter Lite does not support CSV export. The same page has a conflicting Lite reference later in its CSV-limit text; do not use that sentence as a reason to buy Lite for CSV downloads. Confirm availability with LinkedIn before changing a subscription for this task.

Next, check the view: Pipeline CSV, applicant XLSX and profile PDF are separate choices. A missing CSV button in search results does not establish that a project export is unavailable.

For project-profile CSV exports, LinkedIn lists monthly limits of 5,000 unique profiles and 200 CSV files per seat, alongside the 25-candidate selection limit. Profile PDF downloads have a separate allowance of 200 profiles per month per seat; repeat downloads count. These monthly limits reset on a calendar-month basis using UTC.

LinkedIn's applicant-export Help says its applicant XLSX and PDF downloads have no download limit. Do not apply the project-profile caps to that applicant workflow.

For project-profile CSV, LinkedIn describes fields including name, location, current title and company, projects and pipeline stages, and feedback. Project context matters: notes added in a different project do not appear in the export for the current one.

Only contact information entered by a recruiter is included in that CSV. LinkedIn says contact data entered by the member is excluded, regardless of the member's contact settings. An empty email cell therefore does not prove the export failed, and re-downloading the same selection may leave it empty.

Record the gap for the recipient. If a hiring decision depends on notes or an attachment that is absent, keep access to the original hiring record instead of treating the spreadsheet as a complete replacement.

Keep the original export and make a working copy. For a spreadsheet review, agree on the columns the recipient needs. For an import, check the destination's identifier and field rules before removing columns or combining exports.

For example, two rows for the same verified profile might describe different job projects. Keep both in your hiring workbook if both contexts matter. If you need one person in a follow-up list, choose the relevant context deliberately rather than combining notes into an unexplained cell. This is an illustrative review decision, not a sample LinkedIn export.

OutreachGenie's authenticated file importer accepts CSV and XLSX. Each imported prospect needs a public LinkedIn profile URL using a /in/ or /pub/ path. LinkedIn's documented project-profile CSV fields do not promise that identifier. The applicant XLSX field list includes a LinkedIn profile URL, but inspect the actual values before assuming they meet the import requirement.

Prepare one worksheet with no more than 10,000 data rows and 64 columns, in a file of 20 MB or less. XLSX files must contain exactly one worksheet; CSV files must use UTF-8. A wide applicant workbook may exceed the column limit because of its screening questions, so choose the fields needed for this follow-up and review the import warnings.

If a link opens a recruiting view, recover and verify the public profile rather than rewriting its identifier or guessing a URL from the candidate's name. Keep rows without a verified match out of the import until they can be resolved.

The free LinkedIn CSV checker accepts .csv files only and checks them locally in your browser. To use it with a workbook, save a working sheet as UTF-8 CSV first. It can flag missing or invalid public-profile URL formats, repeated profiles and conflicting rows. It cannot verify a candidate's identity, recover missing fields or check an XLSX workbook directly.

In the authenticated importer, inspect field mapping, warnings and existing prospect matches. Use a review list that is not connected to an active campaign, then inspect the resulting records. Existing shared prospects can still belong to other active campaigns, so check their memberships too.

This is a file-import workflow. OutreachGenie does not provide a native Recruiter or Apply Connect integration, and this guide does not establish transfer of resumes, screening answers, hiring evaluations, full note histories or pipeline state. Keep those records in the hiring system. Use the reviewed contact fields only for a relevant, permitted follow-up.