How to use Sorry 100 Times Generator

Edit the main message or choose a template. Add a name only when it improves the message.
Select 10, 50, 100, 500, 1,000 or 10,000 repetitions, or enter a custom whole number.
Open Formatting options only if you need numbering, a custom separator or a special plain-text layout.
Generate the result, review the statistics, then copy the complete output or download a UTF-8 TXT file.

Examples

Numbered lines

1. Sorry
2. Sorry
3. Sorry

Makes the exact count easy to verify.

Specific apology

I’m sorry I interrupted you.
I will listen first.

Specific action can be more useful than volume.

Formal

I apologise for the delay.

A concise work message avoids emotional overstatement.

What the layouts actually do

Straight preserves entry order and your chosen output style. Reverse reverses complete entries, so numbered results count down. Zigzag alternates a four-space indent. Snake moves gradually right and back left. Centered inserts real leading spaces into the copied text instead of using a visual-only CSS effect.

Zigzag, snake and centered always use separate lines. The preview is limited to 50 lines and 12,000 code units for responsiveness; copy and download use the complete result when it remains under the two-million-code-unit safety limit.

Repetition does not replace changed behaviour

A repeated apology may suit a playful context or a formatting task. For a serious issue, name what happened, acknowledge its effect and explain the realistic next step you will take.

If someone asks for space, respect that boundary. A large repeated block should never be used to pressure someone into replying or forgiving you.

Choose the apology for the situation

A playful minor mistake

A short repeated Sorry can fit an inside joke or harmless mix-up when both people understand the tone.

A sincere personal apology

Name the action, acknowledge its effect and state what you will do differently. Repetition should support that message, not replace it.

A professional correction

Use concise wording, accept responsibility and include the practical correction or next step without adding emotional pressure.

Build an apology people can understand

Start with what happened instead of a vague wall of Sorry messages.
Use a lower count for serious situations so the accountable sentence remains readable.
Add a name only when it feels respectful; do not place private details in the generated block.
If the recipient asked for space, save the draft and wait rather than sending repeated follow-ups.

What a complete apology usually includes

Repeating a sincere line can create a playful or visual gesture, but the words still need substance. For anything more serious than a small mistake, build the apology around these five parts.

Name the action
Say what you did without hiding it behind phrases such as “whatever happened.” A clear sentence shows that you understand the actual issue.
Acknowledge the effect
Describe the inconvenience, disappointment or hurt you caused without telling the other person how they must feel.
Accept responsibility
Avoid attaching an excuse to the apology. Context can come later, but responsibility should remain clear.
Offer a realistic repair
Explain what you can correct now: replace something, redo the work, keep a commitment or have a calmer conversation.
Change the next action
A promise matters when it is specific and achievable. State the behaviour you will change, then follow through after the message is sent.

Original apology examples for different situations

Use these as editable starting points. Replace the general detail with what actually happened; do not send a serious apology that you have not read in full.

To a friend

I’m sorry I cancelled so late. I know you set aside time for me. I’ll confirm earlier next time.

Names the missed commitment and a practical change.

To a partner

I’m sorry I dismissed what you were saying. You deserved my attention. I want to listen without interrupting.

Focuses on the behaviour instead of demanding forgiveness.

To a family member

I’m sorry I spoke harshly. That was unfair. I will come back to this conversation when I can speak respectfully.

Sets a calmer next step without pretending the words did no harm.

For a delayed reply

I’m sorry for replying late. I should have let you know I needed more time. Thank you for waiting.

Useful when silence created uncertainty.

For a work mistake

I apologise for sending the incorrect file. I have replaced it, checked the figures and updated the review step.

Includes the correction and prevention step.

For missing a deadline

I’m sorry I missed the agreed deadline. I should have raised the risk sooner. I can deliver the corrected work by Tuesday.

Gives a concrete recovery plan rather than a vague promise.

How many times should you repeat Sorry?

There is no count that proves sincerity. Choose the smallest result that fits the shared context, the destination and the recipient’s preference. You can also set the custom count to 1 and use the generator as an apology formatter.

Count	Possible use	Consider first
1	A serious, complete apology	Often the best choice when the message includes responsibility and a repair.
10	A light mistake or playful exchange	Easy to read and less likely to overwhelm a chat.
50	A deliberate text pattern between people who enjoy that style	Review the complete block before sending.
100	A visible “Sorry 100 times” gesture	Number the lines when the exact count matters.
500	Formatting experiments or an explicitly welcome dramatic gesture	A large block may be inconvenient or treated as spam.
1,000–10,000	Downloads, testing or a mutually understood novelty	Prefer the TXT download. Do not assume a messaging app or recipient wants the full block.

Choose the apology format

Formatting changes readability, not responsibility. These options produce plain text, so the destination may render spaces and emoji differently.

Format	Useful for	Limitation
One per line	Named apologies, exact counts and readable short sentences	Creates the tallest result and may require extensive scrolling.
Numbered lines	Verifying 100 exact entries or making the count visible	Adds characters to every line and can make high counts much larger.
Inline with spaces	Very short text such as Sorry or Sorry 🙏	Long sentences become difficult to scan in one continuous paragraph.
Custom separator	Compact rows separated by a dot, dash, heart or other short marker	Choose a marker that remains clear when copied into another app.
Zigzag, snake or centered	A visual plain-text pattern where leading spaces are part of the result	Alignment can shift in proportional fonts or apps that collapse spaces.

Using emoji without changing the meaning

Emoji can signal tone, but they are not universal and their artwork varies by device. Keep the words understandable even if the symbol is removed or read differently.

Folded hands

Often used for a respectful request or thanks as well as an apology. The exact interpretation depends on culture and context.

Pensive face

Can suggest regret or sadness without adding a strong romantic tone.

Pleading face

Feels vulnerable or playful in close relationships, but can also sound as if you are asking the recipient to comfort you.

Broken heart

Best reserved for a relationship context where emotional hurt is relevant. It may feel exaggerated after a minor practical mistake.

No emoji

Often clearest for workplace, formal or serious apologies. Direct wording can carry the tone without decoration.

Common apology mistakes to avoid

Do not write “I’m sorry you feel that way.” It shifts attention from your action to the other person’s reaction.
Do not add “but” immediately after accepting responsibility. It can turn the apology into a defence.
Do not promise a change you cannot explain or maintain. A smaller specific commitment is more credible.
Do not use thousands of messages to force a reply, interrupt someone’s space or make refusal difficult.
Do not include private names, arguments or identifying details in a public comment or social post.
Do not treat a copied block as proof that the issue is resolved. The recipient decides whether and when to respond.

Before you copy or download

Read one complete generated entry and check the name, spelling and punctuation.
Confirm that the apology names the real issue instead of using a generic sentence.
Check that any repair or promise is realistic and within your control.
Use Preview statistics to understand the number of lines and characters you created.
Reduce the count if the result would be difficult to read or unwelcome in the destination.
Remove private details before posting in a public or shared space.
If someone requested no contact or more time, do not send the generated text.

What to do after sending an apology

Give the person time to read and decide whether they want to respond. Sending additional repeated messages immediately can turn an apology into pressure.

If they reply, listen to what they say before explaining your intention. An apology can acknowledge an effect even when the outcome was not what you intended.

Complete the repair you offered and keep the specific change you promised. Follow-through is the part of an apology that a generator cannot produce for you.

The result is ordinary Unicode plain text. Receiving apps can impose their own message sizes, font choices and anti-spam rules, so review a large result before pasting it. This tool does not send messages, access contacts or place your input in the page URL.

Troubleshooting the generated text

How can I verify there are exactly 100 apologies?

Select 100 and enable Number each message. The result statistics also show the generated repetition count.

Why is only part of a long result visible?

The on-page preview is shortened to protect browser responsiveness. Copy and download still use the complete bounded result.

What if clipboard access is blocked?

The tool reports the failure instead of pretending it copied. Select the visible output manually or use Download TXT.

Frequently asked questions

How do I copy Sorry 100 times?

Keep the message as Sorry, select 100 and use Copy complete output.

Can I add numbers?

Yes. Enable Number each message. Reverse layout then displays the entries in descending order.

Should I send a repeated apology?

Only when it fits the context. Serious apologies usually benefit from specific responsibility and follow-through.

Can I download the result?

Yes. Download TXT saves the complete bounded output as a UTF-8 plain-text file.

Can I create Sorry 1,000 or 10,000 times?

Yes, when the final output remains within the two-million-code-unit safety limit. The preview is shortened, while copy and download use the complete result.

Can I add a person’s name?

Yes. Enter the name and choose a template containing [Name], or type the name directly into the editable message. The value stays in your browser.

Does this tool send the apology for me?

No. It only creates plain text. It cannot open a conversation, contact anyone or confirm that a message was delivered.

Is my apology stored or added to the URL?

No. Generation happens locally in the browser, and message or name values are not added to the page address.

Why might the layout change after pasting?

The receiving app controls fonts, emoji artwork and whitespace. Centered or indented patterns can move when an app collapses spaces or uses a proportional font.

What is better than repeating only the word Sorry?

For a meaningful issue, write what happened, acknowledge the effect, offer a realistic repair and state one specific change you will make.

Write your message

Ready to copy

Start with the right tone