Contact Sales & After-Sales Service

Contact & Quotation

  • Inquire: Call 0086-755-23203480, or reach out via the form below/your sales contact to discuss our design, manufacturing, and assembly capabilities.
  • Quote: Email your PCB files to Sales@pcbsync.com (Preferred for large files) or submit online. We will contact you promptly. Please ensure your email is correct.
Drag & Drop Files, Choose Files to Upload You can upload up to 3 files.

Notes:
For PCB fabrication, we require PCB design file in Gerber RS-274X format (most preferred), *.PCB/DDB (Protel, inform your program version) format or *.BRD (Eagle) format. For PCB assembly, we require PCB design file in above mentioned format, drilling file and BOM. Click to download BOM template To avoid file missing, please include all files into one folder and compress it into .zip or .rar format.

Adafruit Feather Boards: Complete Comparison & Getting Started Guide

If you’ve spent any time evaluating development boards for portable or wireless projects, you’ve probably stumbled across the Adafruit Feather ecosystem. As a PCB engineer who has prototyped dozens of IoT devices, I can tell you that the Feather format solved a problem I didn’t even know I had: the frustration of incompatible board ecosystems, bulky footprints, and the lack of integrated power management.

The Adafruit Feather family isn’t just another development board—it’s an entire ecosystem designed around a standardized form factor. Whether you’re looking at the Feather M0, Feather M4, Feather ESP32, or the newer Feather RP2040, these boards share the same 0.9″ × 2.0″ footprint, compatible pinouts, and a JST connector for LiPo batteries with integrated charging. That means you can swap microcontrollers without rewiring your project or redesigning your enclosure.

In this guide, I’ll walk you through everything you need to know about Feather boards: the key differences between popular models, which one fits your project best, and how to get your first project up and running.

What Makes the Feather Board Ecosystem Special

The Adafruit Feather ecosystem emerged from a simple but powerful idea: create a modular development platform where the microcontroller “mainboard” and add-on “Wings” (FeatherWings) are completely interchangeable. This approach offers several advantages that matter in real-world development.

Standardized Form Factor and Pinout

Every Feather board measures exactly 50.8mm × 22.8mm with 0.1″ mounting holes at each corner. The GPIO arrangement follows a strict specification: a 16-pin strip on one side and a 12-pin strip on the other, with 0.8″ spacing between them. This consistency means that a FeatherWing designed for the original 32u4 Feather will work perfectly with a Feather RP2040 released years later.

Integrated LiPo Battery Management

From a hardware design perspective, this is where Feather boards really shine. Each mainboard includes a Microchip MCP73831 (or equivalent) charge controller with a JST-PH connector. You get proper charging circuitry rated typically for 100-500mA, automatic power source switching between USB and battery, and voltage monitoring through an analog divider on certain models. This eliminates a significant chunk of BOM complexity and PCB real estate that you’d otherwise need for power management.

3.3V Logic Standard

All Feathers operate at 3.3V logic levels. This standardization simplifies interfacing with modern sensors and peripherals, most of which have moved away from 5V logic. If you’re coming from Arduino Uno territory, this is something to keep in mind—but honestly, it’s a benefit, not a limitation.

Adafruit Feather Comparison: Finding the Right Board

Choosing the right Feather depends on your project requirements: processing power, memory, wireless connectivity, and software ecosystem. Let me break down the most popular options.

Quick Comparison Table: Popular Feather Boards

FeatureFeather M0Feather M4Feather ESP32Feather RP2040Feather nRF52840
ProcessorSAMD21 Cortex-M0+SAMD51 Cortex-M4FESP32 Dual-CoreRP2040 Dual Cortex-M0+nRF52840 Cortex-M4F
Clock Speed48 MHz120 MHz240 MHz125-133 MHz64 MHz
Flash256 KB512 KB4-8 MB8 MB QSPI1 MB
RAM32 KB192 KB520 KB264 KB256 KB
WirelessNone (basic)None (Express)WiFi + BT Classic/BLENoneBLE
Native USBYesYesNo (USB-Serial)YesYes
FPUNoYesYesNoYes
CircuitPythonGoodExcellentGoodExcellentExcellent
ArduinoExcellentExcellentExcellentGoodGood
Typical Price$20-25$23-25$20-22$12-14$25

Feather M0: The Reliable Workhorse

The Feather M0 uses the Microchip ATSAMD21G18 ARM Cortex-M0+ running at 48 MHz. It’s essentially the same chip found in the Arduino Zero, which means mature library support and rock-solid stability.

Best for:

  • Projects migrating from Arduino Uno/Leonardo
  • Battery-powered applications where power consumption matters
  • Beginners wanting a stable platform with extensive documentation

The Feather M0 Express variant adds 2MB of SPI flash for CircuitPython file storage and a NeoPixel status LED. If you plan to use CircuitPython, go with the Express version—the extra flash makes a huge difference in usability.

Practical consideration: The M0 lacks hardware floating-point support. If your project involves heavy math (DSP, complex calculations), you’ll feel the performance limitation. The chip handles it through software emulation, but don’t expect to run Fourier transforms efficiently.

Feather M4: Raw Processing Power

The Feather M4 steps up to the SAMD51 processor, a Cortex-M4F clocked at 120 MHz with a hardware floating-point unit (FPU). With 512KB flash and 192KB RAM, it offers significantly more headroom for complex applications.

Best for:

  • Audio processing (I2S, DSP)
  • Display-heavy applications (TFT graphics)
  • Projects requiring floating-point math performance
  • CircuitPython projects with many libraries

The M4’s FPU makes a tangible difference. In my testing, floating-point calculations run about 10-20x faster than on the M0. If you’re doing sensor fusion, audio filtering, or any signal processing, the M4 is worth the extra few dollars.

CAN Bus variant: Adafruit recently released a Feather M4 CAN which swaps to the SAME51 chip, adding hardware CAN bus support. If you’re working in automotive or industrial applications, this is a significant capability.

Feather ESP32: WiFi and Bluetooth in One Package

The Feather ESP32 (specifically the HUZZAH32 and newer V2) packs Espressif’s dual-core ESP32 running at 240 MHz with integrated WiFi and Bluetooth Classic/BLE. The V2 model upgraded to 8MB flash and 2MB PSRAM, plus added a STEMMA QT connector and user button.

Best for:

  • IoT projects requiring WiFi connectivity
  • Bluetooth device communication
  • Web servers and REST API clients
  • Projects with multiple concurrent tasks (dual-core advantage)

Important distinction: The ESP32 doesn’t have native USB—it uses a USB-to-serial converter (CP2104 or CH9102F depending on revision). This means it can’t act as a USB HID device (keyboard, mouse) without additional hardware. If USB functionality matters, look at the ESP32-S2 or ESP32-S3 variants which have native USB.

The ESP32-S3 Feather is particularly compelling if you need both WiFi/BLE and native USB. With dual 240 MHz cores, 8MB flash, and optional PSRAM, it handles CircuitPython and Arduino projects equally well.

Understanding ESP32 Feather Variants

Adafruit offers several ESP32-based Feathers, and the naming can be confusing. Here’s a breakdown:

VariantChipWiFiBLENative USBKey Feature
HUZZAH32 (Original)ESP32YesYes + ClassicNoProven, mature
ESP32 V2ESP32-PICOYesYes + ClassicNo8MB flash, 2MB PSRAM
ESP32-S2ESP32-S2YesNoYesSingle core, USB-OTG
ESP32-S3ESP32-S3YesYes (LE only)YesAI acceleration, USB-OTG
ESP32-C6ESP32-C6Yes (WiFi 6)Yes (BLE 5)NoWiFi 6, Zigbee/Thread

The ESP32-C6 Feather deserves special mention for smart home developers. It supports WiFi 6, Bluetooth 5 LE, and the 802.15.4 protocol (Zigbee/Thread), making it potentially ideal for Matter-compatible devices. If you’re building for the evolving smart home ecosystem, the C6 is worth serious consideration.

Feather RP2040: The Price-Performance Champion

The Feather RP2040 brings the Raspberry Pi Foundation’s RP2040 chip to the Feather ecosystem. With dual Cortex-M0+ cores at 125-133 MHz, 264KB SRAM, and 8MB QSPI flash, it punches well above its weight class at around $12.

Best for:

  • Cost-sensitive projects
  • Learning PIO (Programmable I/O) for custom peripherals
  • Projects needing flexible GPIO mapping
  • Multi-core experimentation

The RP2040’s killer feature is its PIO (Programmable I/O) state machines. These allow you to implement custom serial protocols (like NeoPixel timing or VGA output) without burning CPU cycles. It’s not something beginners typically need, but for advanced projects, PIO opens possibilities that other chips simply can’t match.

Trade-off: No hardware floating-point unit. Like the M0, floating-point operations run in software. However, with two cores, you can dedicate one to computation while the other handles I/O—a capability neither the M0 nor M4 can match.

Specialty RP2040 Feather Variants

Adafruit has released several RP2040 Feathers with integrated functionality:

Feather RP2040 SCORPIO — Includes 8 channels of NeoPixel-optimized PIO outputs. If you’re building large LED installations, this board drives 8 separate NeoPixel strands simultaneously without CPU overhead.

Feather RP2040 with USB Host — Adds a USB Type-A port for connecting USB devices (keyboards, game controllers, MIDI controllers) to your project. This opens entirely new project categories.

Feather RP2040 CAN Bus — Integrates an MCP2515 CAN controller with terminal blocks, ready for automotive or industrial networking projects.

Feather RP2040 Adalogger — Includes a microSD card slot for data logging applications.

Feather RP2040 with RFM95 LoRa — Combines the RP2040 with a 915 MHz LoRa radio for long-range wireless projects.

This variant strategy is one of the Feather ecosystem’s strengths: you get application-specific hardware without leaving the familiar form factor and development environment.

Feather nRF52840: Ultra-Low Power BLE

For Bluetooth-focused projects, the Feather nRF52840 uses Nordic’s nRF52840 SoC—a Cortex-M4F at 64 MHz with excellent BLE 5.0 support. The “Sense” variant adds a full sensor suite (LSM6DS33 accelerometer/gyroscope, LIS3MDL magnetometer, APDS9960 proximity/light/gesture, SHT30 temperature/humidity, PDM microphone).

Best for:

  • Wearables and fitness trackers
  • BLE beacons and peripherals
  • Ultra-low-power battery applications
  • Sensor nodes with Bluetooth connectivity

The nRF52840’s power consumption in sleep modes is exceptional—critical for battery-powered wearables expected to last weeks or months.

Choosing the Right Feather Board: Decision Guide

Here’s my practical decision framework based on common project requirements:

Project TypeRecommended FeatherReason
WiFi-connected IoT sensorFeather ESP32 V2Built-in WiFi, good power management
USB keyboard/mouseFeather RP2040 or M4Native USB HID support
Battery-powered wearableFeather nRF52840Ultra-low power, BLE
Audio/music projectFeather M4 ExpressFPU, I2S, processing headroom
First Feather projectFeather RP2040Low cost, great docs, dual core
LoRa/long-range wirelessFeather M0 RFM95Integrated LoRa radio
CircuitPython learningFeather RP2040 or M4Best CircuitPython support

Getting Started with Your First Feather Project

Let me walk through the practical steps to get a Feather board running. I’ll use the Feather RP2040 as an example, but the process is similar across the family.

Hardware Setup Requirements

You’ll need:

  • A Feather board of your choice
  • USB-C or Micro-USB cable (data cable, not charge-only)
  • Optional: 3.7V LiPo battery with JST-PH connector
  • Optional: Solderless breadboard and headers

Most Feathers ship without headers soldered. You can solder standard 0.1″ headers or use stacking headers if you plan to add FeatherWings.

Arduino IDE Setup for Feather Boards

Step 1: Install Arduino IDE
Download the latest version from arduino.cc. Version 2.x works well with all Feathers.

Step 2: Add Board Support
Open Preferences (File → Preferences) and add the appropriate URL to “Additional Board Manager URLs”:

For SAMD-based Feathers (M0, M4):

https://adafruit.github.io/arduino-board-index/package_adafruit_index.json

For ESP32-based Feathers:

https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json

For RP2040-based Feathers:

https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json

Step 3: Install Board Package
Go to Tools → Board → Board Manager, search for your board family (e.g., “Adafruit SAMD” or “Raspberry Pi Pico/RP2040”), and install.

Step 4: Select Your Board
Under Tools → Board, select your specific Feather model. The exact name matters—”Adafruit Feather RP2040″ is different from generic RP2040 boards.

CircuitPython Setup: The Faster Path

For many projects, CircuitPython offers a faster development cycle. Here’s how to get started:

Step 1: Download CircuitPython
Visit circuitpython.org/downloads and search for your specific Feather model.

Step 2: Enter Bootloader Mode
For RP2040 Feathers: Hold the BOOTSEL button while plugging in USB. A drive named “RPI-RP2” appears.

For SAMD Feathers: Double-click the reset button quickly. A drive named “FEATHERBOOT” or similar appears.

For ESP32 Feathers: The process involves the ESP Tool or Adafruit’s web-based flasher.

Step 3: Install CircuitPython
Drag the downloaded .UF2 file to the bootloader drive. The board reboots, and a new “CIRCUITPY” drive appears.

Step 4: Write Code
Create or edit code.py on the CIRCUITPY drive. The board auto-reloads when you save—no compile step needed.

Installing CircuitPython Libraries

CircuitPython’s power comes from its extensive library ecosystem. To add libraries:

  1. Download the library bundle from circuitpython.org/libraries matching your CircuitPython version
  2. Extract the ZIP file
  3. Copy needed libraries from the lib folder to the lib folder on your CIRCUITPY drive

For example, to use a NeoPixel strip, copy neopixel.mpy to your board’s lib folder. The .mpy files are compiled Python—smaller and faster than raw .py files.

Pro tip: Use CircUp (pip install circup) to manage libraries from the command line. It automatically detects your board and installs/updates libraries.

Your First Blink Program

Arduino (works on any Feather):

cpp

void setup() {  pinMode(LED_BUILTIN, OUTPUT);}void loop() {  digitalWrite(LED_BUILTIN, HIGH);  delay(500);  digitalWrite(LED_BUILTIN, LOW);  delay(500);}

CircuitPython:

python

import boardimport digitalioimport timeled = digitalio.DigitalInOut(board.LED)led.direction = digitalio.Direction.OUTPUTwhile True:    led.value = True    time.sleep(0.5)    led.value = False    time.sleep(0.5)

Expanding with FeatherWings

FeatherWings are stackable add-on boards that plug directly into Feather headers. This modular approach lets you add capabilities without custom wiring.

Popular FeatherWings Worth Considering

FeatherWingFunctionInterface
OLED 128×64Monochrome display + 3 buttonsI2C
TFT 2.4″Color touchscreenSPI
AdaloggerSD card + RTCSPI + I2C
Motor/StepperDrive 4 DC or 2 stepper motorsI2C
GPSLocation trackingUART
EthernetWired network (WIZ5500)SPI
NeoPixel8-channel LED driverGPIO
Prop-MakerAudio amp, NeoPixel, accelerometerMultiple

Most FeatherWings use I2C, making them stackable without pin conflicts. The Doubler and Tripler boards let you mount multiple Feathers and Wings side-by-side for complex projects.

FeatherWing Stacking Considerations

When stacking multiple FeatherWings, watch for these potential conflicts:

I2C Address Conflicts — Some FeatherWings have the same default I2C address. Most include address jumpers to resolve this, but check before purchasing multiple displays or sensors.

SPI Pin Usage — SPI FeatherWings (like displays and SD cards) typically share MOSI, MISO, and SCK but need unique CS (Chip Select) pins. Verify the default CS pin doesn’t conflict with your other peripherals.

Power Draw — Multiple active FeatherWings can exceed what the USB port provides. The TFT displays with backlights, motor drivers, and NeoPixel Wings all draw significant current.

Physical Interference — Taller components on one FeatherWing can interfere with the underside of the next. Use stacking headers with sufficient height clearance.

Common Feather Project Examples

Here are proven project combinations that work well together:

Weather Station (IoT):

  • Feather ESP32 V2 (WiFi connectivity)
  • BME280 FeatherWing or breakout (temperature, humidity, pressure)
  • 128×64 OLED FeatherWing (local display)
  • 400mAh LiPo battery + solar charger for outdoor deployment

Data Logger:

  • Feather M0 Adalogger (built-in SD card slot)
  • RTC FeatherWing for timestamps
  • Sensor of choice (accelerometer, environmental, etc.)
  • LiPo battery for untethered operation

Wearable with Display:

  • Feather nRF52840 Express (BLE for phone notifications)
  • 2.13″ E-Ink FeatherWing (ultra-low-power display)
  • Small LiPo battery
  • Custom enclosure

USB Macro Keyboard:

  • Feather RP2040 (native USB HID)
  • Custom mechanical switches wired to GPIO
  • Optional NeoKey FeatherWing for hot-swap sockets

Audio Player:

  • Feather M4 Express (processing power for audio)
  • Music Maker FeatherWing (VS1053 codec + SD slot)
  • Speaker and amplifier

Power Management Deep Dive

Understanding power is critical for portable Feather projects. Let me break down what’s actually happening on these boards.

LiPo Charging Circuit

All Feathers include a single-cell LiPo charger based on the MCP73831 or similar. Key specifications:

  • Input voltage: 5V from USB
  • Charge current: Typically 100-500mA (varies by board, check your specific model)
  • Termination voltage: 4.2V (standard LiPo full charge)
  • Charge indicator: Red LED on most boards (on during charge, off when complete)

The charger operates automatically whenever USB is connected and a battery is present. You don’t need to manage it in software.

Power Source Selection

Feathers include an automatic power multiplexer. When USB is connected, the board runs from USB power and charges the battery simultaneously. When USB disconnects, the board immediately switches to battery power with no interruption—your code keeps running.

The 3.3V regulator (typically AP2112 or MIC5225) provides stable logic power regardless of input source. USB voltage varies with cable quality and load; battery voltage drops from 4.2V to 3.3V as it discharges. The regulator handles this variation transparently.

Battery Voltage Monitoring

Most Feathers include a voltage divider connecting the battery to an analog input (commonly A6 or A7). Reading this pin gives you battery state information:

python

# CircuitPython battery monitoring exampleimport boardimport analogiobattery = analogio.AnalogIn(board.VOLTAGE_MONITOR)# Voltage divider ratio varies by board – this is for RP2040voltage = battery.value * 3.3 / 65536 * 2print(f”Battery voltage: {voltage:.2f}V”)

A fully charged LiPo reads approximately 4.2V; consider 3.3V as “empty” (though most LiPo batteries should not discharge below 3.0V to preserve cell health).

Deep Sleep and Low Power Modes

For battery longevity, put your Feather to sleep between measurements:

SAMD21/SAMD51 (M0/M4): Use alarm module in CircuitPython or LowPower library in Arduino. Achievable current: ~1-10µA in deep sleep.

ESP32: Use esp32.wake_on_ext0() or esp32.wake_on_touch() in CircuitPython. The ESP32 is power-hungry when WiFi is active but can achieve ~10µA in deep sleep.

RP2040: The dormant and sleep functions in the SDK provide low-power modes, though not as aggressive as dedicated low-power chips.

nRF52840: Optimized for ultra-low-power—expect ~1µA in system OFF with RAM retention.

Practical Tips from Experience

After building numerous Feather-based projects, here are some lessons learned:

Power budget carefully. The built-in charger is typically rated for 100-500mA. If you’re driving NeoPixels, motors, or other power-hungry peripherals, add external power management.

Check pin compatibility. While FeatherWings are generally universal, some use GPIO pins that conflict with specific Feather variants. The ESP8266 Feather, for example, has very limited GPIO flexibility.

Mind your flash usage with CircuitPython. Libraries eat memory quickly. The RP2040 and M4 Express with their large SPI flash handle this well; the basic M0 boards struggle.

Use STEMMA QT connectors. Newer Feathers include STEMMA QT (Qwiic-compatible) I2C ports. This 4-pin connector makes adding sensors trivially easy—no soldering required.

Troubleshooting Common Issues

Board Not Recognized by Computer

Symptoms: No COM port appears, “Unknown Device” in Windows Device Manager.

Solutions:

  1. Try a different USB cable—many cables are charge-only without data lines
  2. Try a different USB port, preferably directly on the motherboard
  3. For ESP32 boards, install the CP2104 or CH9102F driver
  4. For boards with native USB (RP2040, M4, nRF52840), double-click reset to enter bootloader mode

CircuitPython CIRCUITPY Drive Missing

Cause: Board running Arduino code or corrupted filesystem.

Solutions:

  1. Double-click reset to enter bootloader mode
  2. Re-flash CircuitPython
  3. If filesystem is corrupted, use storage.erase_filesystem() from REPL

Can’t Upload Arduino Sketch

Symptoms: Upload times out or fails.

Solutions:

  1. Ensure correct board selected in Tools → Board menu
  2. Check COM port selection
  3. For ESP32-S2/S3, hold BOOT button during upload initiation
  4. For SAMD boards, double-click reset to enter bootloader

FeatherWing Not Responding

Debugging steps:

  1. Run an I2C scanner sketch to verify the device is detected
  2. Check for address conflicts with other I2C devices
  3. Verify power delivery (some Wings draw more current than expected)
  4. Ensure proper library version for your CircuitPython or Arduino version

Useful Resources and Downloads

Here are the resources I keep bookmarked:

Official Documentation:

  • Adafruit Learning System Feather Guide: learn.adafruit.com/adafruit-feather
  • CircuitPython Downloads: circuitpython.org/downloads
  • Arduino Board Packages: github.com/adafruit/Adafruit_Arduino_Boards

Pinouts and Schematics:

  • Each Feather’s Learn Guide includes pinout diagrams
  • GitHub repositories contain KiCad/Eagle files for reference designs

Library Collections:

  • Adafruit CircuitPython Library Bundle: circuitpython.org/libraries
  • Adafruit Arduino Libraries: github.com/adafruit (search for specific sensors/peripherals)

Community Resources:

  • Awesome Feather (GitHub): github.com/adafruit/awesome-feather
  • Adafruit Forums: forums.adafruit.com
  • Adafruit Discord: discord.gg/adafruit

Frequently Asked Questions

What is the difference between Feather and Arduino boards?

Feather boards maintain a standardized form factor (50.8mm × 22.8mm) with consistent pinouts across all variants, regardless of the microcontroller used. They include integrated LiPo battery charging and use 3.3V logic. Arduino boards vary widely in size, pinout, and features depending on the model. The key advantage of Feather is ecosystem compatibility—FeatherWings work with any Feather mainboard.

Can I use Arduino code on a Feather RP2040 or Feather ESP32?

Yes. All Feather boards support Arduino IDE programming with appropriate board support packages installed. However, some Arduino libraries written for AVR chips (like Uno) may need modification for ARM-based or ESP32 Feathers. Libraries from Adafruit are typically tested across the Feather family.

Which Feather board is best for beginners?

The Feather RP2040 offers the best combination of low cost (~$12), excellent documentation, CircuitPython support, and forgiving bootloader behavior. The Feather M4 Express is also excellent if you want more processing power and don’t mind spending slightly more.

How long can a Feather run on battery power?

This depends heavily on the board variant and your code. A Feather M0 in deep sleep can last months on a 400mAh LiPo. A Feather ESP32 with WiFi active might drain the same battery in hours. The nRF52840 excels in ultra-low-power scenarios. Always calculate your power budget based on active versus sleep duty cycles.

Are Feather boards good for commercial or production use?

Many companies use Feather boards for prototyping and low-volume production. For higher volumes, you’d typically design a custom PCB using the same microcontroller while referencing Adafruit’s open-source schematics. The MCP73831 charge circuit and power architecture translate directly to custom designs.

Final Thoughts

The Adafruit Feather ecosystem represents what I wish existed when I started embedded development: a modular, well-documented platform that doesn’t lock you into a single chip architecture. Whether you need the raw power of the Feather M4, the wireless capabilities of the Feather ESP32, the value of the Feather RP2040, or the low-power BLE of the Feather nRF52840, there’s a board that fits.

Start with whichever Feather matches your project needs, knowing that your investment in learning the ecosystem—and any FeatherWings you acquire—will carry forward to future projects. That’s the real power of a standardized platform.

If you’re still unsure, grab a Feather RP2040. At under $15, it’s hard to go wrong, and it’ll teach you everything you need to know about the ecosystem before committing to more specialized boards.

Leave a Reply

Your email address will not be published. Required fields are marked *

Contact Sales & After-Sales Service

Contact & Quotation

  • Inquire: Call 0086-755-23203480, or reach out via the form below/your sales contact to discuss our design, manufacturing, and assembly capabilities.

  • Quote: Email your PCB files to Sales@pcbsync.com (Preferred for large files) or submit online. We will contact you promptly. Please ensure your email is correct.

Drag & Drop Files, Choose Files to Upload You can upload up to 3 files.

Notes:
For PCB fabrication, we require PCB design file in Gerber RS-274X format (most preferred), *.PCB/DDB (Protel, inform your program version) format or *.BRD (Eagle) format. For PCB assembly, we require PCB design file in above mentioned format, drilling file and BOM. Click to download BOM template To avoid file missing, please include all files into one folder and compress it into .zip or .rar format.