If a Star Trek Transporter can remember the physical state of a person it transports from point A to point B, then why couldn't it heal an injured person it has transported back to their uninjured state?

  • I recall an episode in which a transport had gone fatally wrong. The person was subsequently reconstructed from data in the transporter. I'm uncertain which person it was, but I think it was the captain.
    – kasperd
    Jun 5, 2015 at 7:08
  • They could be, provided enough stable memory was available. What else could matter? Dec 14, 2023 at 22:10

5 Answers 5


Theoretically it can.

This was a large topic of discussion in the TNG episode Unnatural Selection (S02E07). In the episode, while quarantined on a shuttlecraft Doctor Pulaski contracts a disease that speeds up her aging process. While the Enterprise staff is coming up with solutions for saving her

...Transporter Chief Miles O'Brien gets an idea: they can use the transporter trace, a previous pattern when she didn't have the disease, to control the way she is reconstituted.

The problem ends up being that she has never used the transporter before, so they find her DNA on a hair follicle from her cabin and use that to reconstruct her pattern through the transporter.

Watch this episode and they go through a lot about using the transporters in the way you've suggested. They don't end up using the pattern trace since it doesn't exist, but they talk about it as a good solution. And they do end up using her DNA pattern and the transporter to heal her of the aging disease.

This was also done in the TAS episode The Lorelei Signal (S01E04), it just wasn't talked about nearly as much.

This presumably isn't attempted more frequently because of the huge risks associated with the process. In both episodes, they talk about the danger of it failing, which would cause the people's molecules to scatter in space. On Unnatural Selection:

Chief O'Brien says it will work, but it would be risky, since they will lose her pattern if it doesn't work.

On The Lorelei Signal:

Spock states that the odds are against them, 99.7 to 1. If it fails, their patterns will break up and scatter in space.

Because of the inherent risk, this seems to be a "nothing else will work and this is our only option" emergency solution. It's less risky to transport someone with a broken leg and have the medical team fix it. If they fail, at least the person wasn't transported out of existence and they're just left with a messed-up leg.

  • 4
    The transporter was also used in TNG Rascals in a similar manner.
    – Xantec
    May 7, 2013 at 14:39
  • @Xantec Good call. I forgot about that episode.
    – SocioMatt
    May 7, 2013 at 14:45
  • Good addition from TAS (which I've never seen). I was considering mentioning Unnatural Selection when I saw this earlier, but couldn't remember if there was talk of failure (which was pretty much required for the answer to make sense).
    – Izkata
    May 8, 2013 at 0:25
  • @Izkata Unfortunately, in other episodes (like TNG S06E07 "Rascals") where they try something like this, they don't talk about the consequences of failure.
    – SocioMatt
    May 8, 2013 at 12:05
  • 1
    @SocioMatt We should all be so lucky to forget
    – IG_42
    Apr 23, 2018 at 22:19

I can't remember which episode, but there's one that mentioned some one's pattern cannot be hold up in transporter more then certain time. It's said prohibited by Federation law. If somehow it does happen, whatever the reason, that pattern must be destroyed (so does the person itself).

Anyway just knowing there's an episode that tried to use transporter to cure someone disease with transporter. Guess it's "legal" if the intention is to save some one's live.

  • From the Memory Alpha page on Transporters: "The transporter trace itself would be stored for the duration of the person's tour of duty; when that person was reassigned, his or her trace would be deleted. (TNG: "Unnatural Selection")" I can't remember them talking about it being against Starfleet regulations anywhere else.
    – SocioMatt
    May 7, 2013 at 17:22
  • And welcome to SciFi SE!
    – SocioMatt
    May 7, 2013 at 17:23
  • I think you have the pattern buffer confused with the transporter trace. The pattern buffer can't hold a person mid-transport for very long (usually just a couple of minutes at most), or it would lose integrity and they couldn't materialize. It was a limitation of the technology, not a law. The transporter trace is as @SocioMatt described.
    – Izkata
    May 8, 2013 at 0:28
  • Did they explain why this limitation exists? I thought once the pattern saved, it should be no problem to save it forever, and technically is capable to re-produce it as many as we like. Basically it's the same technology used by replicator and holodeck, that's I thought the law kicks in to prevent living organism being duplicated un-ethically.
    – a a
    May 8, 2013 at 2:07
  • Wasn't there an episode where Scotty was held in a transporter for a long period of time in TNG, where the other two were scattered due to extended length of time? (because we evidently can't kill off James Doohan! The engines would fail!)
    – Jersey
    May 9, 2013 at 15:39

I remember an episode of Voyager in which they were holding usable biological patterns in a transporter buffer, and they could only hold it there for about a half hour or so, before the patterns would degrade. A transporter is essentially a giant replicator, and it's a well known fact that replicators can't reproduce complex organic matter. The way that I've always thought of it was that during transport, your body was streamed from location to your destination, much like a radio stream of the internet. We humans are so big that you couldn't possibly store people in the main computer's storage devices, so the buffers are put into place for a consistent read/write time. It would suck if you had to buffer while you were materialization.

I don't think the transporter system would have the time to make the bulk edits needed to say, remove the cancer from your body. Think of zip files, when you edit one file, you have to uncompress the entire thing, then recompress the new file. Voyager's crew managed to do the transporter magic trick thing maybe three times, before there was biological repercussions. You'd probably do more harm then good.

  • A replicator is essential a cut back transporter that can work from stored data, but a transport is so much more than a replicator. To put it another way, all squares are rectangles, but all rectangles are not squares.
    – T.J.L.
    May 17, 2021 at 18:46

There are hints that the memory capacity needed for transporter patterns is massive even for future technology.

The assumption that all electronic memories are digital and essentially stable over an arbitrary amount of time, in the worst case by making a perfect copy (also, the assumption you can always perfectly copy them!), is newer than most canon-defining ST material.

In the 1960s, going digital when not needed would likely have been a somewhat absurd notion for an engineer even when imaging technology hundreds of years into the future.

--- What follows is real life electronics geekery, for comparison ---

Even in the 1960s to 1990s, finding unquantized ANALOG signals (that are subject to degradation in storage in some way or another) to be the most economic storage encoding was common. There were audio and video tapes, one-line glass-stick delay line memories in PAL televisions and VCRs, analog image stores like Radechon tubes or DVBST displays in professional applications (jam-proof RADAR, 1970s computer graphics terminals, fast data acquisition), long-persistence phosphors in radar CRT screens, bucket-brigade analog delays (in 1980s musician's delay units), analog CCDs (in high speed data acquistion), semiconductor based but ANALOG audio storage microchips (eg the ISD1016 series). All of these provided a MORE economic solution than quantizing and digitizing, then storing digitally on a medium that could have held more analog data, then converting back to analog, the data that needed storing. Note: quantizing = translating a real-life measure into something that can be expressed as a writable number. Not all digital signals are quantized (eg a PWM signal might not be), not all analog signals are truly unquantized (modern flash memory for SSDs and USB sticks often use a kind of quantized analog format internally).

Even many (not all!) real life digital storage systems rely on cancelling decay effects by regularly replacing the data with a perfect copy for the data to last. DRAMs used in modern computers do. Mass storage systems like HDD or SSD only do so accidentally and occasionally. Anything that can store a lot AND very fast is likely to need it. Unquantized data can neither be kept truly perfect for ANY length of time, nor can any copy of it ever be perfect (the ever-present noise will see to that).

Also, digitizing a very large amount of data will always give you a timing disadvantage - think of a real life camera sensor. While it can capture a, say, 12 megapixel (ca. 40 megabyte, assuming 3 channels a 8 bits) image at a 1/10000th second shutter speed (actually, most camera shutters don't work quite that way, but that is irrelevant here) - it is usually not capable of digitizing and transferring into memory all of that image in 1/10000th second (which would need a bandwidth of 400 gigabytes/second. Which would even today be an extra tall order, above what would be economical in the average camera). Using an analog signal would seemingly land you in similar trouble here - but in both cases the solution would be "use more parallel channels" (eg all rows or columns in parallel on a wire each), and working with analog end-to-end here could still prove the more cost effective solution if speed but not permanent storage was desired (say, 2048 100MHz video channels vs 2048 equally fast 8 bit flash or SAR ADCs. Both are nightmare fuel.).

In something (eg a living being) that moves internally on all levels, accepting timing skews by not imaging everything at the same time won't go well.

Even today, a system that would need short-term data storage capacity beyond what is possible/economic in a digital way would be likely implemented in an analog manner at the very frontend.

  • I know you're only using it as an example, but you've got the way a digital camera sensor works wrong. Digital camera sensors work in grayscale, and many will use 12-14 bits per photosite to represent luminosity (basically, number of photons captured by that photosite during the exposure). In front of each photosite is a color filter. The image data is only later turned into a color image by interpolating nearby photosites and adding knowledge of the color filter layout, along with applying a white balance. With JPEG output, all this happens in the camera; with RAW, in post-processing.
    – user
    Apr 24, 2018 at 8:19
  • "In something (eg a living being) that moves internally on all levels, accepting timing skews by not imaging everything at the same time won't go well." I agree, which is why it bothers me when we see people moving around inside the transporter beam, or even showing evidence of cognition and sight (!) like Barclay. The thing was portrayed a little inconsistently. Sep 21, 2019 at 21:47
  • "In something (eg a living being) that moves internally on all levels, accepting timing skews by not imaging everything at the same time won't go well." I agree, which is why it bothers me when we see people moving around while under transport, or even showing evidence of cognition and sight (!) like Barclay. The thing was portrayed a little inconsistently. Sep 21, 2019 at 21:47
  • Not hinted - flat out stated in the TNG Technical Manual - molecular vs. quantum resolution.
    – T.J.L.
    May 17, 2021 at 18:45

The episode 'Unnatural Selection' is one of those stupid canon breaking episodes that should never have been resolved as it did.

The showrunners should have made the writers come up with a better solution to the illness Dr Polaski and the other scientists had. Using the transporter to cure the illness and make them young again was just plain lazy writing. It is a canon breaker because it makes curing someone sick a relatively simple task. As long as there is a pre sickness transporter trace then anyone ill, or even injured, can be simply run through the transporter and they come out perfectly healthy again.

Worse, it could also be used to restore someone to a younger age, making death obsolete. As long as you've got a trace from when you were younger, who wouldn't treat themselves to a yearly birthday present of going through a transporter and coming out a year younger again.

Even worse, it can be used to clone someone. All you would need is some energy and a transporter trace and out pops a clone of that person.

And even worse than that, it could be used to bring a dead person back to life. The dead could simply be put into the transporter and as long as there is a pre-death transporter trace they can simply be reanimated.

According to most official Star Trek resources the transporters are supposed to work like this; the person or object is scanned, then the molecules are converted into sub-atomic energy particles, these particles are briefly stored in the pattern buffer, then directed to a transporter emitter array, from there the matter stream is transmitted through a subspace domain to the destination, finally the energy particles are converted back into matter and the person or object rematerialises.

This means a sick person rematerialises sick, an injured person still needs medical attention, no one stays young forever, no clones, and the dead stay dead!

This is also why a person can't be stored in the transporter forever. The matter stream can only be held in the transporter buffer for a few minutes maximum. After that, the sub-atomic particles start to decay and the pattern degrades. If the pattern degrades too much the person cannot be rematerialisation fully and/or alive.

When the pattern has degraded too far there are only three things that can happen. One, it can be redirected back to an emitter and rematerialised as a cloud of individual atoms in space. Two, it can be left to decay into nothing inside the buffer. Or three, what is left can be rematerialised with a large amount of missing molecules. That means whatever is being transported will be 'incomplete'. An object would come with bits missing and a person would come out as a messy organic lump.

So the answer to your question is no, it cannot be used to heal an injured person. Unless of course, the story is being written by a lazy writer.

  • "As long as there is a pre sickness transporter trace then anyone ill, or even injured, can be simply run through the transporter and they come out perfectly healthy again." Not really; the disease in that episode specifically worked by altering DNA. If we assume for the sake of argument that that makes any sense, then the scenario in the episode isn't so crazy, and it also isn't really related to the question which seems to be more like "why can't they store a copy of the person from yesterday, then rematerialise them with the leg they lost this morning"... Sep 21, 2019 at 21:41
  • ... the answer, of course, being (a) storage space, and (b) ethics. See also: Thomas Riker. But being able to manipulate DNA in the transporter stream (using a reference point from a hair sample) is not the same as magically fixing any ailment. Sep 21, 2019 at 21:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.