Random Name Picker

Our team ever tested 200k names, which cost the server 10-15 seconds to generate the winner. 100k names will cost 5 seconds. If your list is less than 50k names, it should get the winner instantly.

Yes, it is quite random. It is because we use server-side, not Javascript from users' local computers, to generate the random winner. And with our innovative 3-step Randomness Process Certification, it is almost impossible to change the winner by a person or malicious code.

When you click Pick a Random Name button, the tool will submit all names line by line to our server. Then our server will use Python random module to generate one pseudo-random number between 1 to total names. Then it will choose the name with this random number as a winner.

Both are the same from the technical part - the random function from Python and Javascript both generate pseudo-random numbers.

However, it is a different story on actual real-world operations:

If using random function from Javascript, as the full source codes are stored on users' local computers, it is impossible to prevent a malicious code or any person from doing something to bypass the random function and set a value to the "winner" directly. It can happen in the background process, which other people can not see on the screen. It is something which the developers can not control.

We don't want that somebody use our tool to raffle off a prize, but bypass the random process, and record a video to say, "Hey, we picked a random winner by a tool from miniwebtool.com." So we choose a server-side solution.

By using server-side random function, the only thing that the malicious code or a person can change is the data source. For this situation, you can use our 3-step Randomness Process Certification to prove that the whole process is clean and "random."

If you use Random Name Picker for raffles, contests, drawings, giveaways, and promotions, etc., you are encouraged to enable 3-step Randomness Process Certification function to improve your credibility.

For example, you use the name picker to raffle off a prize to 99 people from John Doe No. 001 to 099:

The winner is John Doe No. 090, here is Demo of The Server-side Certification Link.

Our server will store a part of the information, including the winner's name (asterisked), total names, timestamp, and a SHA512 hash code.

This is step 1. When you give this link and the full winner name to your attendees, most people will trust that your raffle is random.

However, what if somebody doesn't like the winner, and want to check whether there are many duplicate John Doe No. 090 in your original name list?

In this case, you can go to step 2 to download your client-side certification file to prove that your data source has no error. Here is Demo of The Client-side Certification File link.

Finally, what if another John Doe doubt you have modified the file?

You can let him go to step 3, use our SHA512 Hash Generator to check the downloaded file. The SHA512 hash code should be the same if the file did not be changed.

A person can use a fake screenshot or video to change the winner name from local computers, but can not change the information stored on our server. With the firmly secure SHA512 Hash, It is almost inconceivable that any modified file can pass step 3 verification.

It is the reason that you can gain more credibility using our 3-step randomness process certification.

Yes, it is easier from technical part but we can not do it due to our privacy policy. We never store any data visitors submit, because the data may contain lots of personal information. We recognize that the privacy of everybody's personal information is essential.

Some users want to use the picker many times with the same name list; for example, teachers pick up a name from students. So we use the HTML5 Web Storage technique to make their life easier. With web storage, web applications can store data locally within the user's browser. If you use a public computer and do not want your names stored, you can use private or incognito window from your browser or submit another some Meaningless text. (We only use web storage to store the last submitted information.)