# How do I enable unbuffered logging in UE5?

**URL:** <https://forums.unrealengine.com/t/how-do-i-enable-unbuffered-logging-in-ue5/1151301>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, question\
**Created:** [May 2, 2023, 12:14am UTC](https://forums.unrealengine.com/t/how-do-i-enable-unbuffered-logging-in-ue5/1151301 "2023-05-02T00:14:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ParanoidDroid12](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ParanoidDroid12](https://forums.unrealengine.com/u/ParanoidDroid12)\
**Post date:** [May 2, 2023, 12:14am UTC](https://forums.unrealengine.com/t/how-do-i-enable-unbuffered-logging-in-ue5/1151301/1 "2023-05-02T00:14:26Z")

</div>

Running the Linux server build of UE5 and observing that log output to stdout is being flushed every 4k.

Is there a configuration to disable buffering of log output to stdout? If not, what are my options for writing output unbuffered to stdout?

---

<div class="post-metadata">

**Author:** ![MikeSeese](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mikeseese/32/1022829_2.png) [@MikeSeese](https://forums.unrealengine.com/u/MikeSeese)\
**Post date:** [December 19, 2025, 10:27pm UTC](https://forums.unrealengine.com/t/how-do-i-enable-unbuffered-logging-in-ue5/1151301/2 "2025-12-19T22:27:57Z")

</div>

I know I’m necrobumping this but I ran into this also.

It looks like `Engine/Source/Runtime/ApplicationCore/Private/Linux/LinuxConsoleOutputDevice.cpp` is what’s handling the logging to stdout here. There is no manual flushing so standard `stdout` buffering will defer here. If you’re running the UE server without a TTY (not via a terminal, e.g. in Kubernetes or Docker), it’s up to the compiler implementation, which typically is 8k or 4k in our case. So you can either attach a TTY to defer to line-buffering (flushes after `\n` or manually add `fflush(stdout)` after the `printf`.

Another potential option is to use the CLI flag `-stdout`, which will defer to the `FOutputDeviceStdOutput` device in `Engine/Source/Runtime/Launch/Private/LaunchEngineLoop.cpp`, which already has a `fflush(stdout)` after each line, though it seems like the logging is more limited in this mode.

A totally separate solution (which is what I went with) is use a 3rd party program like `stdbuf -oL -eL <program>` to force line buffering for both stdout and stderr
