# Switch a Proxy Between HTTP and SOCKS5 | ProxyJam

Yes. Switch the order you already hold between HTTP and SOCKS5 with Change protocol or one API call, then copy the new port and credentials.

- Canonical: https://proxyjam.com/faq/switch-proxy-protocol/
- Updated: 2026-11-22
- Language: en

Yes. Every static ISP proxy runs HTTP, which carries HTTPS, or SOCKS5, and you switch the order you already hold. Use Change protocol in your dashboard or the protocol call of the API. The order then shows the port and credentials to use after the switch, so copy them again, and expect a brief pause while it switches.


## Quick answers about switching protocol

### Does switching change my IP?

Switching changes the protocol, port and credentials of the order you hold. The address is the one issued for the order, and Terms of Service, section 2.5, says it is not replaced during the paid period.

### Do I need a new order for SOCKS5?

No. The same order is switched. A new order is only needed for a different IP address.

### Which protocol should I pick?

The one your client needs. Our SOCKS5 page compares the protocols, so this page does not repeat it.



Protocol is a setting of the order, not a separate product. You do not buy HTTP proxies and
SOCKS5 proxies apart: the one you hold can be switched to either, and changing the client
alone is not enough, because the proxy itself has to listen in the other protocol. Which of the two fits a given tool is explained on the
[SOCKS5 proxies](/socks5-proxies/) page.

## How to switch

1. Open **My Proxies** in your [dashboard](https://app.proxyjam.com).
2. Choose **Change protocol** on the proxy and pick HTTP or SOCKS5.
3. Wait for the row to update, then copy the host, port, login and password again.
4. Put the new values into every client that uses this order.

From code, the call is `POST /orders/{order_id}/protocol` with `new_type` set to `HTTP` or
`SOCKS5`, documented on the
[Change proxy protocol page](https://docs.proxyjam.com/api/orders/proxy-change-protocol). The response
carries the updated host, port and credentials, and the Python SDK exposes the same call.

## What changes and what does not

The documentation says the record is updated with the new protocol, port and credentials
returned after the switch, and that the proxy may briefly be unavailable while it switches.
Plan it for a quiet moment, and do not run a long job across it.

The address is the one issued for the order. Section 2.5 of the
[Terms of Service](/terms-of-service/) says the IP is not replaced during the period you paid
for, and a switch does not start a new order.

## If it stops working after the switch

Most failures come from a mismatch: the order is on one protocol and the client is set to the
other, or the client still holds the old port. Compare the row with the client's settings, as
[proxy not working](/faq/proxy-not-working/) describes. To see which protocol the proxy answers on
now, paste the new details into our [proxy checker](/proxy-checker/) with the protocol on Auto: the
result names the one that worked. A client that keeps asking for a
password may have been set to a protocol that cannot send one; the post on
[proxy authentication](/blog/proxy-authentication-methods/) lists which clients can do what
over SOCKS5, and [error 407](/faq/proxy-error-407/) covers a refused sign-in.

For two worked setups, see [SOCKS5 in Telegram](/faq/telegram-socks5-proxy/) and
[a proxy on iPhone](/faq/proxy-on-iphone/). The Telegram guide starts with this switch; the iPhone guide needs it only for an app that takes SOCKS5.

