Back to Articles
Comparison2026-05-20•5 min read•CSR.plus Team

CSR Generator vs. OpenSSL: Which CSR Workflow to Use

CSR Generator vs. OpenSSL: Which CSR Workflow to Use

CSR Generator vs. OpenSSL: Choosing Your CSR Workflow

There are two practical ways to generate a Certificate Signing Request (CSR) for a TLS certificate (still widely called SSL): OpenSSL on a server, or a browser-based CSR Generator. Both produce valid PKCS#10 requests and both are accepted by every certificate authority — they differ in workflow, error surface, and where the private key lives. For one-off website certificates the browser workflow is faster and harder to get wrong; OpenSSL still wins for automated pipelines.

The Two Workflows at a Glance

AspectOpenSSL (CLI)CSR Generator (browser)
PrerequisitesServer/terminal access, OpenSSL installedAny modern browser
Required knowledgeCommand syntax, file paths, key formatsFill in a web form
Private key locationServer disk (manage permissions yourself)Your device only, never uploaded
Input validationNone — errors surface at the CAField-level checks as you type
SAN configurationExtra flags or a config fileExtra form fields
Best forScripting, CI/CD, bulk issuanceOne-off and ad-hoc requests

What the OpenSSL Route Looks Like

The classic one-liner is openssl req -new -newkey rsa:2048 -nodes -keyout server.key -out server.csr -subj "/C=US/ST=California/L=San Jose/O=Example Inc/CN=example.com". It works, but SANs need extra -addext flags or a config file, interactive prompts differ between OpenSSL versions, and a typo in -subj silently produces a wrong subject — you may not notice until the CA has issued a certificate for the wrong name.

What the Browser Route Looks Like

Open the CSR Generator, type your domain and organization details into labeled fields, pick RSA or ECC, and click generate. The form validates formats as you type — country codes, hostname syntax — and both files download instantly. The key pair is created with the browser's built-in cryptography, entirely on your device.

Where Your Private Key Lives

Both routes keep the private key local, which is the only correct design. The difference is ergonomics: with OpenSSL the key lands in your current working directory with default permissions; the browser workflow hands you both files explicitly and prompts you to store the key safely. In neither case is anything sent to a server.

When OpenSSL Is Still the Right Choice

Keep the CLI for scheduled issuance, ACME clients such as Certbot, provisioning scripts, and any environment where a human should not be in the loop. For everything else — new sites, renewals without automation, testing, helping a colleague — a browser-based generator removes the failure modes of hand-typed commands.

How to Switch Workflows in Five Steps

Step 1: Pick the Route That Fits the Job

One certificate for a site you manage by hand → browser. Dozens of certificates or CI automation → OpenSSL/ACME.

Step 2: Generate with the CSR Generator

Open the CSR Generator, enter the common name, add SANs, choose the key type, and download the CSR and private key.

Step 3: Or Generate with OpenSSL

Run the command above, then double-check the subject with openssl req -in server.csr -noout -subject before submitting.

Step 4: Verify Either Output the Same Way

Paste the CSR into the Certificate Decoder. You should see the exact hostname, SANs and key algorithm you intended — regardless of which route produced it.

Step 5: Confirm the Match After Issuance

After the CA returns the certificate, run the Certificate & Key Matcher to prove it pairs with your key, and finish with the SSL Checker once it is installed.

Troubleshooting Checklist

SymptomLikely causeHow to fix
unable to load config infoOpenSSL can't find its config fileSet OPENSSL_CONF or reinstall with default config
No value provided for subjectEmpty -subj string or wrong quotingQuote the whole subject; or use the browser form instead
CA issues certificate for the wrong nameTypo in -subj CN or missing SAN flagsVerify the CSR in the Certificate Decoder, then regenerate
OpenSSH: permissions 0644 for 'server.key' are too openKey file world-readablechmod 600 server.key
CSR carries the old organization nameReused config file with stale fieldsEdit the config or generate a fresh CSR from scratch
Passphrase demanded at every restartKey generated without -nodesDecrypt the key once or regenerate unencrypted

FAQ

Is a browser-generated CSR less secure than OpenSSL?

No. Security depends on where the key pair is created, not on which interface you typed it into. The CSR Generator creates keys locally with the browser's crypto engine and never transmits them; a carelessly permissioned OpenSSL key on a shared server is far riskier.

Do certificate authorities accept both?

Yes. Both routes emit standard PKCS#10 requests defined in RFC 2986, and every CA accepts them. The CA cannot even tell which tool generated a given CSR.

Can I generate ECC keys with OpenSSL?

Yes: `openssl ecparam -genkey -name prime256v1 -out server.key` followed by `openssl req -new -key server.key -out server.csr`. The browser route offers the same curves in a dropdown.

Which workflow should a small team standardize on?

Use the browser generator for anything a human touches and OpenSSL/ACME for anything automated. Document both, and require a decode check before every submission.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles