# Eagle2Fritzing needs updating

**URL:** <https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824>\
**Category:** developers\
**Created:** [February 24, 2026, 3:20pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824 "2026-02-24T15:20:44Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![RAPTOR7762](https://forum.fritzing.org/user_avatar/forum.fritzing.org/raptor7762/32/22620_2.png) [@RAPTOR7762](https://forum.fritzing.org/u/RAPTOR7762)\
**Post date:** [February 24, 2026, 3:20pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/1 "2026-02-24T15:20:44Z")

</div>

Hi developers, @KjellM @fai

I’m currently concerned about the phase-out of EAGLEcad in June 7 2026, because the current old Eagle2Fritzing may not work. Many organisations (like Adafruit) are reliant on Eagle2Fritzing.

Hemce, I’m proposing a python version of Eagle2Fritzing. I think it’s easier to use, and doesn’t need heavy Qt installation or Fritzing software compilation. Maybe it can go

```auto
Eagle2Fritzing.py filename.brd

```

in a terminal. Then the python script can look for subparts in a subparts folder, and make the SVG. What are your thoughts

---

<div class="post-metadata">

**Author:** ![Harald\_Rau](https://forum.fritzing.org/user_avatar/forum.fritzing.org/harald_rau/32/21072_2.png) [@Harald\_Rau](https://forum.fritzing.org/u/Harald_Rau)\
**Post date:** [February 24, 2026, 6:58pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/2 "2026-02-24T18:58:46Z")

</div>

Oh yes, that would be great. Wasn’t there something like that before? I thought I had already worked with that in a 9.x version of Fritzing.  
Regards, Harald!

---

<div class="post-metadata">

**Author:** ![fai](https://forum.fritzing.org/letter_avatar_proxy/v4/letter/f/87869e/32.png) [@fai](https://forum.fritzing.org/u/fai)\
**Post date:** [February 25, 2026, 8:57am UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/3 "2026-02-25T08:57:10Z")

</div>

Hi!

I think Eagle user base is decreasing as Autodesk is tightening the free options. I am not sure if Adafruit is still using it to develop their boards. In any case, eage2fritzing should still work.

Thus, investing precious developer time in improving eage2fritzing seems not very efficient.

I see two better alternatives.

1. Create a kicad2fritzing. Kicad is open source and it contains a lot of importing tools. It can import boards from eagle. Thus, you could import your eagle board to Kicad and then import the Kicad board to fritzing.

1. Finishing the part editor in fritzing. Not exactly the same as importing a board made in a different cad tool, but it could ease the problem.

---

<div class="post-metadata">

**Author:** ![RAPTOR7762](https://forum.fritzing.org/user_avatar/forum.fritzing.org/raptor7762/32/22620_2.png) [@RAPTOR7762](https://forum.fritzing.org/u/RAPTOR7762)\
**Post date:** [February 25, 2026, 11:23am UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/4 "2026-02-25T11:23:10Z")

</div>

Ive done some sketchy work, but

> **[GitHub - RAPTOR7762/convert2fritzing-python](https://github.com/RAPTOR7762/convert2fritzing-python)**
>
> Contribute to RAPTOR7762/convert2fritzing-python development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![Harald\_Rau](https://forum.fritzing.org/user_avatar/forum.fritzing.org/harald_rau/32/21072_2.png) [@Harald\_Rau](https://forum.fritzing.org/u/Harald_Rau)\
**Post date:** [February 25, 2026, 12:22pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/5 "2026-02-25T12:22:30Z")

</div>

Thanks, I’ll try it shortly.

---

<div class="post-metadata">

**Author:** ![RAPTOR7762](https://forum.fritzing.org/user_avatar/forum.fritzing.org/raptor7762/32/22620_2.png) [@RAPTOR7762](https://forum.fritzing.org/u/RAPTOR7762)\
**Post date:** [February 26, 2026, 11:16am UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/6 "2026-02-26T11:16:23Z")

</div>

I don’t think that one works because I simply haven’t fully programmed it

---

<div class="post-metadata">

**Author:** ![Harald\_Rau](https://forum.fritzing.org/user_avatar/forum.fritzing.org/harald_rau/32/21072_2.png) [@Harald\_Rau](https://forum.fritzing.org/u/Harald_Rau)\
**Post date:** [February 26, 2026, 12:52pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/7 "2026-02-26T12:52:38Z")

</div>

Ah, no rush. I now understand how to get the footprint out of KiCad.

All the little add-on parts for the breadboard view are great. I think Peter also had a whole pool of them.

Where can I find these parts?

---

<div class="post-metadata">

**Author:** ![RAPTOR7762](https://forum.fritzing.org/user_avatar/forum.fritzing.org/raptor7762/32/22620_2.png) [@RAPTOR7762](https://forum.fritzing.org/u/RAPTOR7762)\
**Post date:** [February 26, 2026, 2:31pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/8 "2026-02-26T14:31:08Z")

</div>

He send me a long time ago, I would need to dig those. Btw may I PM you about more things on this project (Maybe I should call it convert2fritzing-python

---

<div class="post-metadata">

**Author:** ![Harald\_Rau](https://forum.fritzing.org/user_avatar/forum.fritzing.org/harald_rau/32/21072_2.png) [@Harald\_Rau](https://forum.fritzing.org/u/Harald_Rau)\
**Post date:** [February 26, 2026, 2:54pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/9 "2026-02-26T14:54:22Z")

</div>

Yes, of course!

I’m waiting for the message.

---

<div class="post-metadata">

**Author:** ![KjellM](https://forum.fritzing.org/letter_avatar_proxy/v4/letter/k/a3d4f5/32.png) [@KjellM](https://forum.fritzing.org/u/KjellM)\
**Post date:** [February 28, 2026, 10:33am UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/10 "2026-02-28T10:33:30Z")

</div>

Hi @RAPTOR7762

I wonder what the idea of the eagle2fritzing-python is. You just want to replace the existig tool? When eagle is not supported anymore, I expect there will be less eagle files to import from. And for the existing eagle files… well for old projects, just use the old tool?

---

<div class="post-metadata">

**Author:** ![KjellM](https://forum.fritzing.org/letter_avatar_proxy/v4/letter/k/a3d4f5/32.png) [@KjellM](https://forum.fritzing.org/u/KjellM)\
**Post date:** [February 28, 2026, 10:41am UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/11 "2026-02-28T10:41:05Z")

</div>

I think these breadboard subparts are from the eagle2fritzing tool. While on it, I think some of them have invisible (zero sized) SVG elements, that are a little annoying. That could be an easy improvement to clean them up.

---

<div class="post-metadata">

**Author:** ![RAPTOR7762](https://forum.fritzing.org/user_avatar/forum.fritzing.org/raptor7762/32/22620_2.png) [@RAPTOR7762](https://forum.fritzing.org/u/RAPTOR7762)\
**Post date:** [February 28, 2026, 3:19pm UTC](https://forum.fritzing.org/t/eagle2fritzing-needs-updating/33824/12 "2026-02-28T15:19:09Z")

</div>

Hi @KjellM I’ve been tweaking some things and ran into a few issues. The XML library in Qt (xmlpatterns) has been deprecated, and Autodesk Fusion 360 has now replaced the old EAGLE app. Many people—especially Adafruit and SparkFun users—will likely continue using EAGLE for now, and Autodesk Fusion in future

The old Eagle2Fritzing tool launches the original EAGLE app, so if EAGLE stops working after June, the tool may not work either.

I’m also adding KiCad converters to the new tool I’m creating. For clarity, I’ve renamed the repository to **Convert2Fritzing**.
