Sort lines descending

The response returns both a joined text block ready to copy and a structured lines array for APIs, plus counts and echoed options you can pin in tests. Empty input fails with invalid input so pipelines never store blank payloads by accident.

What descending line sorting means and when to use it

Do not use it when you need ascending A–Z as the primary mode, locale-aware collation with accents, natural numeric order such as item 12 before item 2, or an array API with BCP-47 locale tags—those are different products and different search intents.

Input contract, empty rejection, and reading the response

Trailing newlines produce a trailing empty segment that sorts among other lines by reverse string order, matching how many editors expose an extra empty row at the end of the file when reverse-sorting. Send a JSON body with the required string field text set to the non-empty sample you want sorted reverse-alphabetically. Aliases input, value, s, content, body, and lines are accepted when older clients or form generators use those names. Missing text, a non-string value, or a zero-length string all raise invalid_input with a message that names the problem, and those failures are not charged on the prepaid API. There is no order parameter because this landing is dedicated to descending Z–A only; the response always echoes order as desc so UIs and tests can assert the contract without re-reading the request. Optional case_insensitive is a boolean defaulting to false; aliases ignore_case and ci work the same way. On success the response includes text as the sorted lines joined with a single line feed character, lines as the ordered array of segments from Z toward A, and count as the number of segments after the split so you can assert length without re-parsing. case_insensitive echoes the effective option after defaults, original echoes the exact input for before-and-after displays, and method is always sort_lines_descending so downstream code can branch without sniffing shapes. Use text when a human or clipboard needs one paste-ready block; use lines when an SDK will map each row into a table or database insert. Keep payloads to ordinary message and document sizes suitable for a Worker isolate rather than multi-megabyte dumps; this product is a text utility, not a bulk file warehouse.

API usage, pricing, workflows, and practical limits

Call the free in-browser sort lines descending tool for reverse rankings, Z-first glossaries, packing lists that should end with A, name lists for last-letter-first review, changelog bullets that need Z–A cleanup, and quick reverse-alphabetical checks without installing a desktop editor plugin or writing a one-liner in every language. A typical workflow pastes unsorted product names, sorts descending case-insensitively, then copies the joined text field back into a spreadsheet or markdown table so Z-leading brands appear first. Do not expect deduplication, natural numeric order, or language-specific accent rules here—those are separate problems with separate SEO terms. Use the prepaid KIT API when a CMS, content pipeline, QA harness, or mobile client needs the same contract under balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with line counting when the next step is reporting how many rows you reverse-sorted, but keep sort lines descending as its own landing so the sort-lines-descending search intent is not mixed with reverse physical line order, locale list collation, or full spreadsheet sort. Authors shipping SDKs can document text as the only required field, show a multi-line success example with case_insensitive true, and include an empty-string error example so integrators see both sides of the contract.