.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 accounts. No telemetry.
No email signup. No analytics scripts. Files are wiped within 30 minutes of upload and never used for training or resale. The CLI is available for fully offline use on Pro and Lab plans.
0%
51 / 51 public CCNA labs
47 / 47 shipped containerlab examples
all round‑trip cleanly
47 / 47 shipped containerlab examples
all round‑trip cleanly
Free if you’re a student. Fair if you’re not.
The free tier is metered by a first-party cookie with a network-IP backstop — no email required, and no browser fingerprinting. It’s a soft limit: be reasonable, and we are.
Free
for the student, the curious, the “does this even work?”
$0
forever
- 2 free conversions, no signup
- Sign up free for 5/month
- All 6 formats, both directions
- Up to 5 devices per lab
- Files up to 4 MB
- batch upload
- api access
Pro
for the network engineer, the lab author, the consultant
$9
/ month
or $79 / year
- Unlimited conversions
- Batch upload — drop a folder, get a zip
- CLI tool (beta) for scripting and automation
- REST API (token‑authenticated)
- Files up to 100 MB
- Custom mapping rules
- Email support
Lab
for the bootcamp, the network team, the air‑gapped lab
$49
one‑time
perpetual licence · buy once, use forever
- Everything in Pro
- Self‑hosted Docker image — runs in your own network
- Files never leave your infrastructure
- Unlimited internal users
- 1 year of updates included
- Email support
Common questions.
How do you stop people from extending the free tier with new accounts?
The free tier is metered with a first-party cookie, backstopped by your network IP address. It’s a deliberately soft limit — not bulletproof, but enough to raise the cost of farming free conversions above the cost of just paying $9. We don’t fingerprint your browser and we don’t require email signup, precisely because we’d rather not collect what we don’t need.
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 Pro CLI (currently in beta) is a thin client over our conversion API — you authenticate once with your account token and the CLI uploads, converts, and downloads in a single command. It’s built for scripting, batch jobs, and CI pipelines, not for fully‑offline use.
If you need true air‑gapped conversion (no calls leaving your network), that’s the Lab plan: a self‑hosted converter you run inside your own infrastructure on perpetual licence.
Which Packet Tracer versions are supported?
Verified through Cisco Packet Tracer 9.x. Earlier versions usually decode without issue; later versions are best‑effort — if Cisco changes the save format in a future release we issue an update for Pro and Lab subscribers.
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