.pkt
Cisco Packet Tracer
.pkt · .pka · .pkz
Convert any network lab to any tool.
Packet Tracer, GNS3, Containerlab, EVE‑NG, CML2, and netlab — pick any source, pick any target. Configs preserved end‑to‑end. No vendor lock‑in.
No signup · no email
Files wiped in 30 minutes
No telemetry · no tracking
don't have a file?
click any card to convert it
Try one from the gallery.
Three steps. Under a minute.
From a lab file you already have, to one your other tool can open — without the manual rebuild.
-
01
Drop a lab file
Any of the six supported formats. We detect the source format from the file’s content, not its extension.
-
02
Pick a target
Choose one output format — or several. We’ll emit them in parallel. Devices, links, and configs come through intact.
-
03
Download & open
Ready in seconds. Open the result in your target tool — the topology renders with every link UP and every IOS config replayed.
Six formats. Any direction.
Pick any source. Pick any target. Configs and topology come through intact.
.gns3
GNS3
.gns3 · .gns3project
.yaml
Containerlab
.clab.yaml
.unl
EVE‑NG
.unl
.yaml
Cisco Modeling Labs
.cml.yaml
.yml
netlab (ipspace)
.yml · .yaml
Your file is read into a shared topology, then re‑emitted into the target format. Configs, interfaces, and link endpoints come through intact.
Built for engineers who work across tools.
CCNA students
Build the topology in Packet Tracer at school. Study in GNS3 or Containerlab on your own laptop — same lab, different tool, zero rework.
Network engineers
Move between Containerlab in CI, EVE‑NG for training, and GNS3 for client demos — without rebuilding the topology each time.
Lab authors & instructors
Author your courseware once. Ship the lab to students in whichever format their machine supports — Packet Tracer, GNS3, EVE‑NG, or open‑source clab.
Built for engineers who actually use these tools.
01
Configs preserved.
IOS running‑configs survive every round trip — .pkt → .clab → .pkt, .pkt → .unl → .pkt, all five directions. When a source has no IOS to carry, we synthesise the minimum needed to bring the links up.
02
Verified in real apps.
Outputs open in real Cisco Packet Tracer 9.x and deploy on real Linux Containerlab hosts. Not “passes our own parser” — actually loads in the target tool with every link UP.
03
No signup to convert. No telemetry.
No account needed to start converting — upload and go. No analytics scripts. Files are wiped within 30 minutes of upload and never used for training or resale. Optional free accounts unlock API keys, CLI automation, and saved projects.
0%
51 / 51 public CCNA labs
47 / 47 shipped containerlab examples
all round‑trip cleanly
47 / 47 shipped containerlab examples
all round‑trip cleanly
Common questions.
Do I need an account to convert files?
No account is needed to start converting — simply upload your lab and download the converted files. Optional free accounts allow you to generate API keys, access the CLI, and save your projects across devices.
What happens to my uploaded files?
Files are processed in memory and the original, intermediate, and output are written to ephemeral storage that is wiped within 30 minutes. We don’t train models on your files. We don’t resell them. We don’t look at them unless you email us a bug report with one attached.
Does it really preserve IOS running‑configs?
Yes, end‑to‑end. pkt → clab → pkt, pkt → gns3 → pkt, pkt → unl → pkt, pkt → cml → pkt all preserve IOS text byte‑for‑byte. When a source has no IOS to carry — a hand‑authored .gns3 JSON, say — we synthesise the minimum needed for the topology to come up.
What about the CLI tool — does it run conversions on my machine?
The CLI tool is a lightweight client over our conversion API — authenticate once with your account token and the CLI uploads, converts, and downloads in a single command. It is built for scripting, batch jobs, and CI pipelines.
Which Packet Tracer versions are supported?
Verified through Cisco Packet Tracer 9.x. Earlier versions usually decode without issue; later versions are supported through active compatibility updates.
Is this legal? Doesn’t the .pkt format belong to Cisco?
We don’t ship any Cisco code, and we don’t redistribute Cisco files. Reading a file format you legitimately own a file in, for the purpose of interoperability, is generally permitted under the same reverse‑engineering exemptions that let LibreOffice read .docx or ffmpeg read MP4. If your jurisdiction differs, talk to a lawyer.
from the maker
I’m a third‑year telecom student. I built labconvert because I kept rebuilding the same network lab in five different tools to study for the CCNA — Packet Tracer at school, GNS3 at home, Containerlab in a friend’s setup. That should not have been a thing.
— Joey · joseph@labconvert.tech