Quick answer: Long runs fail for two reasons, not one. Copper resistance rises with every extra meter, so the current a PoE device draws arrives with less voltage and more heat. At the same time, each pair leaks a little signal into its neighbors, and that interference matters more as length grows. Before you order a long Ethernet cord, estimate both budgets: resistance for power, crosstalk for data. Whichever runs out first sets your real maximum distance.
You plug a long Ethernet cord into a camera at the far end of a warehouse, and the link trains at a lower speed or drops when the heater kicks on. The cord is not defective. Length alone changes two things at once: the voltage arriving at the device and the noise coupling between pairs. This guide shows how to budget both before you buy, so a long run behaves like a short one.
Where the resistance budget goes
Resistance is the cost of pushing current through copper. A longer cord puts more copper in the path, so the same powered device sees a larger drop and the cord itself warms up. On a plain data link that drop rarely matters; on a powered device at the far end it decides whether the unit boots.
Conductor size sets the floor
Two cords of the same length and category can carry different loads when their conductors differ in gauge. Thicker conductors spread the current across more metal, so they run cooler and deliver more voltage at the far end. When a listing says a long cord suits power over Ethernet, treat conductor gauge as the first number to confirm, not the last one.
PoE current turns resistance into heat
Heat climbs faster than current does, so a device with a heavy draw hurts twice as much on a long run. Bundled cords trap that heat, and a coil left on a reel traps it further. Keep long powered runs unbundled, away from hot ceiling voids, and feel the plug ends after a few hours of load.
Where the crosstalk budget goes
Crosstalk is signal from one pair arriving on another. Every cord has some, but the effect grows with length because the wanted signal reaches the receiver weaker while the leaked signal keeps adding up along the run.
Near end and far end are different problems
Leakage near the transmitter is loud compared with the signal being sent. Leakage near the receiver competes with a signal that has already traveled the full length. Long cords expose both ends. That is why a cord that passes a short bench test can still trigger retransmissions at the end of a 40 m run: the test never asked the far end to work hard.
Why shielding only helps sometimes
A foil or braid shield blocks interference from outside the cord, which matters beside motors, lifts and power feeders. It does not remove coupling between pairs inside the same jacket. If your problem is pair to pair, a better category or cleaner termination is the fix; a shield on its own will not restore the margin.
A simple way to compare long cords
Work in distance bands rather than one maximum figure. Each band tells you which budget is under pressure and what to check on the listing.
| Run band | Resistance pressure | Crosstalk pressure | What to buy |
|---|
| Under 10 m | Negligible | Negligible | Any category that matches the port |
| 10 to 30 m | Low unless the load is heavy | Starts to show on marginal hardware | Cat6 with full copper conductors |
| 30 to 60 m | Visible on PoE draws | The usual cause of retries | Cat6a, or Cat6 with care |
| Beyond 60 m | Main limit for powered devices | Main limit for speed | Shielded Cat6a, short as possible |
Practical scenarios
- Warehouse camera on a 50 m drop: the unit reboots at dawn when heaters come on. Check the PoE draw, then move to a thicker conductor or add a mid span switch.
- Garden office link: speed is fine but calls stutter. Termination quality matters more than shielding here, so inspect the plugs first.
- Loft access point: a coiled surplus length sits beside a warm flue. Cut it to length, because that coil is both a heat trap and an antenna.
- Temporary event run: a cord crosses a walkway and gets stepped on. Use a heavier jacket and strain relief at both ends, not the category rating.
FAQ
Does a longer cord always mean slower speed?
No. A good long cord on clean hardware often negotiates the same speed as a short one. The risk is margin: the longer run has less headroom, so a small fault shows up as retries or a link that drops under load.
Can I join two long cords to reach the distance I need?
A coupler adds its own loss and one more point where pair geometry can shift. It is fine for a temporary link, but treat a permanent joint as a last resort and prefer one continuous cord.
Should I buy shielded long cords for outdoor use?
Shielding helps with outside interference on noisy routes, but does nothing for pair to pair coupling inside the cord. Outdoor runs also need a sunlight rated jacket and proper shield grounding.
Next step
Measure the actual distance first, then check the Cat6a cable specifications overview for what each construction is rated to carry. For noisy or long powered routes, compare a shielded Cat6a Ethernet cable and read the Cat6 vs Cat6a differences before you commit to a length.
See the matching cables and adapters
