Wrap Each Line in Quotes
Wrap every line of text in a quote character, with an optional trailing comma.
How Wrap Each Line in Quotes works
Paste a list of items — one per line — and this tool wraps each line in the quote character of your choice: double quotes, single quotes, backticks, or any custom character you enter. It's useful for quickly turning a plain list into a quoted array for code ("apple", "banana"), building a SQL IN (...) clause, or preparing a JSON/YAML-style list by hand. Toggle "Add trailing comma" to append a comma after each quoted line so you can paste the result straight into an array literal, and toggle "Skip empty lines" to leave blank lines untouched instead of quoting them. Everything runs locally in your browser — nothing you paste is ever uploaded. Use Prefix / Suffix Adder for arbitrary text instead of quotes, or Lines to Comma-Separated to join the quoted lines onto a single line afterward.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Turning a pasted list into an array literal for code or a config.
- Preparing a column of values for a SQL IN clause.
- Quoting a list of filenames so a shell handles spaces correctly.
- Building a JSON array from a plain list of lines.
- Adding trailing commas so a list can be pasted straight into source.
Frequently Asked Questions
- What is this for?
- Turning a plain list into a syntactically valid array literal — a column pasted from a spreadsheet into a JavaScript, Python or SQL list. It is the mechanical half of a job that is otherwise a lot of end-of-line clicking.
- Single or double quotes?
- Whichever the target language prefers: double for JSON, which permits nothing else; single for Python and most JavaScript style guides. SQL string literals are single-quoted and SQL identifiers are double-quoted, so the two are not interchangeable there.
- What happens if a line already contains a quote?
- It has to be escaped or the literal terminates early. That is the one case where wrapping mechanically produces broken output, so check lines containing apostrophes — names and contractions are where it bites in real data.
- Should there be a trailing comma on the last line?
- JavaScript, Python and modern PHP all allow it, and it keeps a diff to one line when an item is appended. JSON forbids it outright, and that is the single most common reason a hand-edited JSON file fails to parse.
- Is there a simpler way for a long list?
- Often, yes. `split('\n')` on a template literal in JavaScript, or a triple-quoted string with `.splitlines()` in Python, keeps the data readable and avoids quoting every line at all. Wrapping is best when the result has to be a literal in source.
Common errors and gotchas
- Not escaping quotes that already appear inside a line, which breaks the literal.
- Leaving a trailing comma on the last item in a format that forbids it, such as JSON.
- Quoting blank lines, which produces empty strings you did not intend.
- Overlooking trailing whitespace, which ends up inside the quotes.
- Choosing double quotes for shell input where they still allow expansion, when single quotes were wanted.