Skip to the content
2 layers376 × 100 mmBeach Board PCB File, the printed circuit board in 3D

First custom keyboard by me for the Hackclub KEEB Program.

Size
376 × 100 mm
Copper layers
2
Thickness
1.6 mm
Parts
169
Nets
124
Pads
891
Tracks, vias
1,040, 190
Pours
6
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
31 Jul 2026
Updated
16 Oct 2026

Overview

Beach Board PCB File is an open-source printed circuit board by harshithrayarvj-web, from the harshithrayarvj-web/Beach-Board repository on GitHub. It is a 2-layer board of 376 × 100 mm with 169 parts on 124 nets, routed with 1,040 tracks and 190 vias.

Its parts include 68 diodes, 8 switches, 4 resistors, 3 capacitors and 2 connectors. It belongs with the keyboards and input boards and the RP2040 boards of this library.

README

README.md

Beach-Board

Journals are separate files in the repo!

They contain most of the extra details

A very dynamic and adaptable keyboard meant to pack as many punches as it can within it's relatively small form factor. Contains a raspberry pi pico, 68 hot-swapable switches, en ec11 rotary encoder, an sd card socket, and a TFT LCD, while being meant to operate on QMK. Screenshot 2026-08-10 220419

The idea behind it

As much as modern keyboards have numerous shortcuts and even gestures for other inputs, I felt that a centralized unit that could do almost all of those things, and more, could be very useful to quickly do things in a straight forward way, similar to a streamdeck. I plan on leveraging the keyboard layout to make it more moldable and flexible for complex tasks, even if they have many smaller details. Along with this I wanted to expand on how screens could be used on keyboards, instead of basic simple screens that show just one type of data, such as WPM, without much flavor, I wanted to have a screen that could potentially both add to the aesthetics of the keyboard, and provide a functional use depending on the task at hand. The theme of a beach themed "surf board" was because of my first long term profile picture that I drew, it helped me create an identity online, so I wanted to hint at that with my first proper project being a keyboard.

Characteristics of keyboard

  • 68 switches (epomaker creamy jade)
  • TFT LCD - animations and information
  • 16mb USB C Pi Pico
  • Hotswap sockets
  • Ortholinear
  • Microsd card socket - expanding storage
  • ec11 Rotary Encoder
  • QMK (keyboard intended to be easily customizable and versatile)

Schematic

Screenshot 2026-08-07 152231

PCB (silkscreen)

Screenshot 2026-08-04 191510 Screenshot 2026-08-04 191330

Firmware (MAINLY WIP)

Screenshot 2026-08-09 140202 Need to remake the layout due to losing the tab and being unable to use the other file, or I need to test it on the website again. Keyboard layout needed to make Firmware development easier with the QMK configurator.

Notes

The keyboard's case was designed with a good amount of clearance to make up for any tolerance issues, but that might lead to fitment issues, so try to use glue or filler items to help the keyboard come together cleaner. Although the large parts are made with clearance in mind, smaller parts like the screen support might have tight clearances, so don't be afraid to sand it down or cut off some extra bits of plastic if they don't fit. Pay attention to how and where the small components solder to (resistors, capacitors, or the mcp), and make sure the solder doesn't short. Try to keep an eye on how high the pico sits on the board to not make it hit the case or put too much stress on the pins if the pins are slightly off from spec, pushing them down too far might put stress on the attachment points for the pins on the pico.

Reflection

Although the project is overall much simpler than what I aim to do for the future, it definitely helped me kick start PCB designing and showed me how to make a finished product (for the most part). It isn't perfect, and I knew that, especially since how rigid hardware can be could affect it's versatility and how future proof it is, meanwhile software can be improved constantly, and that's why I aimed for a mostly software centric keyboard, and looking back I think my fears are pretty exaggerated and unfounded in some areas, but my general prediction was true, and my lack of skill with designing parts for the case, mounting holes, or clearances showed a lot, however it is something I wish to improve on for future projects, and my keyboard showed me some issues I can look at for now.

I think the main difficulty with the project that's worse than designing the hardware was rather finding the parts that were cheap but reliable to get, as some parts seemed cheap but did not have a reliable stock, or had enormous shipping fees (though I did have to compromise on a few things for that due to no other alternatives, and a large portion of cost came from shipping itself unfortunately from things like JLPCB and Aliexpress). This project has showed me where to start now with planning for parts and the overall components I could realistically use, something that's harder to be flexible with than even designing parts for a project, like designing the case around a certain screw/hot insert dimension.

There were also easy things that I really enjoyed to do, like placing down the footprints for the pcb, routing, adding silkscreen art, and designing some simple sections of the hardware (especially decoration, like the waves on the screen case), they were mostly enjoyable outside of trying to find settings or tools for a specific action, but I learned to use onshape and kicad decently now.

Overall, this project really helped me jump into designing something functional and useful, letting me learn to use software like onshape and kicad, and create a BOM and work out issues with how realistic it would be, the experience is really valuable for future projects I plan on doing. The risks I took for this project like using a TFT LCD and a Microsd socket were confusing and scary due to the probability of missing something essential or something that would protect them, but the risk seems worth it as now I know about pull up resistors, decoupling capacitors, ground pour, and how to better go about routing and placing components to make them as clean as possible (but I won't lie, I like how my PCB looks rendered in white with the routes from the MCP, minus the large amount of small route sections visible, but I'm sure cleaner routing is better looking). Using my experience so far, I wish to make more projects and have them come into the real world, hopefully pushing them to be more and more reliable, efficient, and compact.

Parts

169
QtyValueFootprintReferences
681N4148Diode_THT:D_DO-35_SOD27_P7.62mm_HorizontalD1, D2, D10, D11, D12, D13, D14, D15, D16, D17, D18, D19, D20, D21, D22, D23 +52
68MX_SW_HSPCM_marbastlib-mx:SW_MX_HS_CPG151101S11_1uMX1, MX2, MX10, MX11, MX12, MX13, MX14, MX15, MX16, MX17, MX18, MX19, MX20, MX21, MX22, MX23 +52
8LOGOLOGOG***, G***, G***, G***, G***, G***, G***, G***
6MountingHoleMountingHole:MountingHole_2.2mm_M2H1, H2, H3, H4, H5, H6
30.1ufCapacitor_SMD:C_0603_1608MetricC1, C2, C3
3MX_stabPCM_marbastlib-mx:STAB_MX_P_2uS1, S2, S4
3MX_stabPCM_marbastlib-mx:STAB_MX_2uS3, S5, S7
210KResistor_SMD:R_1206_3216Metric_Pad1.30x1.75mm_HandSolderR1, R2
24.7KResistor_SMD:R_1206_3216Metric_Pad1.30x1.75mm_HandSolderR3, R4
1Conn_01x08_PinConnector_PinSocket_2.54mm:PinSocket_1x08_P2.54mm_VerticalJ1
1MCP23017x-x-SOPackage_SO:SOIC-28W_7.5x17.9mm_P1.27mmU1
1MX_stabPCM_marbastlib-mx:STAB_MX_P_7uS6
1Micro_SD_CardConnector_Card:microSD_HC_Molex_47219-2001J2
1RaspberryPi_PicoModule:RaspberryPi_Pico_Common_THTA1
1RotaryEncoder_SwitchRotary_Encoder:RotaryEncoder_Alps_EC11E-Switch_Vertical_H20mmSW1

Similar boards

  • 2 layers410 × 128.5 mmFranklin ace-1000-keyboard, the printed circuit board in 3D

    Franklin ace-1000-keyboard

    osiweb/unified_retro_keyboard

    Project to provide keyboard replacements for various classic computers, as well as classic ASCII keyboard

    169 parts122
  • 2 layers281 × 108.3 mmPDP8, the printed circuit board in 3D

    PDP8

    douggilliland/Retro-Computers

    Retro-Computer Designs (Z80, 65C816, etc)

    169 parts87
  • 2 layers148.6 × 192.2 mmBadge, the printed circuit board in 3D

    Badge

    NuttyShell/NuttyBadge

    NuttyBadge: A NuttyShell crafted multi-tool. Opensourced Hardawre and Software

    169 parts31GPL-3.0
  • 2 layers284.7 × 94.2 mmStoryboard, the printed circuit board in 3D

    Storyboard

    cbskii/storyboard-keyboard

    5x12 split ortholinear keyboard with an E-INK display

    169 parts30MIT
  • 2 layers90 × 109 mmInterface 303, the printed circuit board in 3D

    Interface 303

    jeanpri/303

    303 eurorack interface for x0x-heart

    169 parts23
  • 2 layers301.9 × 106.3 mmXavien gateron millmax, the printed circuit board in 3D

    Xavien gateron millmax

    yyevax/xavient-kbd

    xavient is a thin split mechanical keyboard that does not sacrifice repairability and upgradablility. Inspired by the sleek design of the Corne-ish Zen but with hotswappalbe switches and components.

    169 parts22CC-BY-4.0
  • 2 layers174 × 111 mmPedalboard hw, the printed circuit board in 3D

    Pedalboard hw

    pedalboard/pedalboard-hw

    pedalboard audio midi processor open hardware

    169 parts14CERN-OHL-P-2.0
  • 2 layers285.1 × 94.6 mmYuTofu PCB, the printed circuit board in 3D

    YuTofu PCB

    ymkn/YuTofu

    YuTofu is an unofficial compatible PCB for the well-known custom keyboard Tofu60 2.0.

    169 parts5MIT

Questions

How big is the Beach Board PCB File PCB?

It measures 376 × 100 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Beach Board PCB File use?

169 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Beach Board PCB File KiCad files?

From the harshithrayarvj-web/Beach-Board repository on GitHub, at the commit this page was made from: the board is Beach-Board PCB File.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the Beach Board PCB File design in my own project?

Its repository states no licence, so its author keeps all rights: ask harshithrayarvj-web before reusing the design.