Sample Feather File
A downloadable sample Feather (Arrow IPC) file with 30 fictional employee records, deliberately uncompressed so every reader — including browser tools — can open it.
sample-employees.feather
Data Preview
| 1 | name | department | role | salary | start_date | office | |
| 2 | Marcus Chen | marcus.chen@example.com | Engineering | Senior Software Engineer | 155000 | 2019-03-15 | San Francisco |
| 3 | Priya Sharma | priya.sharma@example.com | Engineering | Staff Engineer | 178000 | 2019-06-01 | San Francisco |
| 4 | David Kim | david.kim@example.com | Engineering | Software Engineer | 125000 | 2021-01-10 | New York |
| 5 | Rachel Torres | rachel.torres@example.com | Engineering | Engineering Manager | 168000 | 2020-02-20 | San Francisco |
| 6 | James Okafor | james.okafor@example.com | Engineering | Junior Developer | 92000 | 2024-06-15 | Austin |
| 7 | Lena Vogt | lena.vogt@example.com | Engineering | DevOps Engineer | 140000 | 2022-04-01 | New York |
| 8 | Amir Patel | amir.patel@example.com | Engineering | Backend Engineer | 132000 | 2023-01-09 | London |
| 9 | Sofia Lindberg | sofia.lindberg@example.com | Design | Lead Designer | 145000 | 2019-09-12 | New York |
| 10 | Carlos Rivera | carlos.rivera@example.com | Design | UX Designer | 112000 | 2021-07-20 | San Francisco |
| 11 | Hannah Becker | hannah.becker@example.com | Design | UI Designer | 105000 | 2022-11-01 | London |
| 12 | Yuki Tanaka | yuki.tanaka@example.com | Design | Product Designer | 118000 | 2023-03-14 | San Francisco |
| 13 | Olivia Martin | olivia.martin@example.com | Marketing | VP of Marketing | 165000 | 2019-04-22 | New York |
| 14 | Ethan Brooks | ethan.brooks@example.com | Marketing | Content Strategist | 95000 | 2021-10-05 | Austin |
| 15 | Nina Kowalski | nina.kowalski@example.com | Marketing | SEO Specialist | 88000 | 2022-08-15 | New York |
| 16 | Daniel Ochoa | daniel.ochoa@example.com | Marketing | Marketing Analyst | 91000 | 2023-05-20 | Austin |
| 17 | Samira Hassan | samira.hassan@example.com | Marketing | Social Media Manager | 82000 | 2024-01-08 | London |
| 18 | Tyler Washington | tyler.washington@example.com | Sales | Sales Director | 158000 | 2019-11-30 | New York |
| 19 | Jessica Huang | jessica.huang@example.com | Sales | Account Executive | 110000 | 2020-06-14 | San Francisco |
| 20 | Ryan O'Brien | ryan.obrien@example.com | Sales | Account Executive | 105000 | 2021-03-22 | London |
| 21 | Fatima Al-Rashid | fatima.alrashid@example.com | Sales | Sales Development Rep | 72000 | 2023-09-01 | Austin |
| 22 | Kevin Dupont | kevin.dupont@example.com | Sales | Solutions Engineer | 135000 | 2022-01-17 | San Francisco |
| 23 | Megan Stewart | megan.stewart@example.com | Sales | Account Manager | 98000 | 2024-03-11 | New York |
| 24 | Laura Chen | laura.chen@example.com | HR | HR Director | 148000 | 2019-08-05 | New York |
| 25 | Brian Nakamura | brian.nakamura@example.com | HR | HR Business Partner | 105000 | 2020-12-01 | San Francisco |
| 26 | Chloe Dubois | chloe.dubois@example.com | HR | Recruiter | 78000 | 2022-05-23 | London |
| 27 | Angela Moretti | angela.moretti@example.com | HR | People Operations | 85000 | 2023-07-10 | Austin |
| 28 | Isaac Fernandez | isaac.fernandez@example.com | Engineering | Frontend Engineer | 128000 | 2022-09-19 | New York |
| 29 | Sarah Mitchell | sarah.mitchell@example.com | Design | Design Systems Lead | 138000 | 2020-04-06 | San Francisco |
| 30 | Omar Farah | omar.farah@example.com | Engineering | QA Engineer | 95000 | 2024-02-12 | London |
| 31 | Natalie Park | natalie.park@example.com | Marketing | Growth Manager | 108000 | 2021-11-28 | San Francisco |
Schema
| Field | Type | Description |
|---|---|---|
| name | string | Employee full name. |
| string | Work email address on the fictional example.com domain. | |
| department | string | One of Engineering, Sales, Marketing, HR, or Design. |
| role | string | Job title within the department. |
| salary | int32 | Annual salary in USD, stored as a 32-bit integer column. |
| start_date | string | Hire date as an ISO 8601 string (YYYY-MM-DD). |
| office | string | Office location — San Francisco, New York, Austin, or London. |
About the Feather Format
Feather (v2) is the Apache Arrow IPC file format: Arrow’s in-memory columnar layout written to disk essentially verbatim, with a schema block up front and record batches behind it. Files carry .feather, .arrow, or .ipc extensions interchangeably — they are the same format.
Because the on-disk bytes match Arrow’s in-memory representation, reading Feather is close to a no-op: a reader can memory-map the file and use the buffers directly, with zero parsing and zero copying. That makes it the fastest way to move a dataframe between processes and languages — pandas to polars, Python to R — when both ends speak Arrow. The embedded schema travels with the data, so salary arrives as an int32 column with no type inference, same as the Parquet sample.
This sample is deliberately uncompressed. Feather supports optional LZ4 and ZSTD compression of record batches, and many writers enable it by default — but browser builds of the apache-arrow JavaScript library ship without those codecs, so compressed files fail in web tools with a codec error. Writing with compression='uncompressed' keeps the file readable by every Arrow implementation, including the site’s own Feather to CSV converter. At 30 rows the size cost is irrelevant; at scale, you’d enable ZSTD for storage and accept the narrower reader support.
Feather versus Parquet is a recurring question, and the honest answer is: Parquet for storage (heavier encoding and compression, broad ecosystem, predicate pushdown), Feather for interchange (minimal encode/decode cost, exact Arrow fidelity). If you need this data as Parquet, convert via CSV to Parquet or inspect it in the Parquet Viewer.
All eleven format samples in this section carry the same 30 employee rows, so converted output can be checked against the CSV baseline.